Carpenter - Intro to Computer Science (Section Thur 5)

Instructor
Anne Carpenter
Department
Technology
Terms
2019-2020 School Year


Assignment Calendar

Course Description

 

Class Title:

Intro to Computer Science

Code:

MEL986

Text:

Code.org

Rating:

2

Prerequisite:

Computer Skills or equivalent

Grade:

7-­8

Fees:

None

Max:

15

Can be repeated? No

Description: Students will jump into the world of computer science and learn all about computers, processes, data, and how they all work together. Students will look at problem-solving, web development, interactive games and animations, the design process, data and society, and physical computing. Students will have both unplugged and plugged activities to learn about concepts. Internet access at home is required.

Posts

Week of February 17: Intro to Computer Science

What We Did:

  • We started our multi-page website project
  • This project will take a few sessions to complete

2.9: Project: Multi-Page Websites

  • Connect multiple web pages into one website using hyperlinks

After learning about how to link web pages to one another, students are finally able to publish the website they have been working on. In this lesson, they link together all the previous pages they have created into one project, create a new page, and add navigation between the pages

What to Work On:

  • Any unfinished work- please email me when you are done
  • Code.Org code studio- 2.6 and 2.8 

What We Plan to Do Next Week:

  • Continue to work on our project 

Week of February 10: Intro to Computer Science

What We Did: 
  • 2.8: Debugging and Clean Code 

Students deal with common issues that arise when designing web pages in HTML. Students will correct errors in a sequence of increasingly complex web pages. In the process they will learn the importance of comments, whitespace, and indentation as tools for making web pages easier to read. At the end of the lesson students create a list of strategies for debugging web pages and ensuring they are easy to read and maintain.

  • Describe why using whitespace, indentation, and comments makes your code easier to maintain
  • Develop a set of techniques for preventing bugs in HTML code and finding them when they occur

What to Work On:

  • Finish 2.8 in the Code Studio if you haven’t finished it
  • Hour of Code 

What We Plan to Do Next Week:

  • 2.9: Multi-Page Websites

Week of February 3: Intro to Computer Science

What We Did:

  • 2.7: Intellectual Property and Images
    • Explain the purpose of copyright.
    • Identify the rights and restrictions granted by various Creative Commons licenses
    • Add an image to a web page

What to Work On:

  • Any unfinished coding in the Code Studio 
  • Hour of Code

What We Plan to Do Next Week:

  • Clean Code and Debugging 

Week of January 27: Intro to Computer Science

What We Did:

  • 2.6: Lists
    • Use the <ol>, <ul>, and <li> tags to create ordered and unordered lists in an HTML page.
    • Create and name a new HTML page.

What to Work On:

  • Think about what you would like to include in your website design 
  • Optional- Khan Academy:  Intro to HTML 

What We Plan to Do Next Week:

  • 2.7: Intellectual Property and Images 

Grading Reminder

Grading reminder: This year we have begun to put “Missings” into the Infinite Campus Gradebook if student’s work is not turned in at the time we grade.  We were asked to do this by the office. I will make a note if a student is absent or if something is incomplete. I always welcome my students to keep working on their assignments if they are unhappy with the grade they earned.  The goal is to learn and keep growing their skills, so I’m happy if they’d like to go back and make improvements to their work. If a student is absent, I will send home missing work and they need to let me know when they’ve “turned it in” in their folder online via email.  Missings can be changed easily and do not have to be the final grade if the students re-submits or turns in their work for the first time if they were sick. We want students to understand what happens if they don’t complete work, which is why we have been asked to put in the missings.  And like I said, this can be changed easily once students hand in their work. At the end of the semester students will be told a date in advance for when grades will be finalized. This will give them time if they have any missing assignments to complete them and turn them in. While my goal is for students to learn, it is also a goal for students to stick to deadlines, be responsible for their work, etc. I would highly encourage them to stay up to date with their assignments. Please let me know if you have any questions about this. 

Week of January 20: Intro to Computer Science

What We Did:

  • 2.5: Digital Footprint 
    • Understand and explain reasons that it is difficult to control who sees information published online.
    • Understand and justify guidelines for safely publishing information online.

What to Work On:

  • Think about what else you’d like to include in your website
  • What kind of lists could you use for your website? 

What We Plan to Do Next Week:

  • 2.6: HTML Lists 
    • Use the <ol>, <ul>, and <li> tags to create ordered and unordered lists in an HTML page.
    • Create and name a new HTML page.

Week of January 13: Intro to Computer Science

What We Did:

  • Reviewed HTML on Khan Academy with HTML Basics 
  • 2.4: Headings 
    • <h1> through <h6> and their differences
    • <p> tag for paragraph work 

What to Work On:

What We Plan to Do Next Week:

  • 2.5: Digital Footprint 

Week of December 13

Happy Holidays! We had a great week wrapping things up, sharing work, and celebrating the semester with a party.  It was so much fun seeing art show and the performances and all of our talented students! Have a great holiday break with your families.  My family is looking forward to spending time together and relaxing.  See you in the new year! 

Week of December 9: Intro to Computer Science

What We Did:

What to Work On:

What We Plan to Do Next Week:

  • Wrap up any unfinished work
  • Hour of Code, playing with HTML 

Week of December 2: Intro to Computer Science

What We Did:

  • Students began designing their own websites in their journal- they will transfer this later to code 
  • 2.2: Websites for Expression
    • Identify websites as a form of personal expression
  • 2.3: Intro to HTML 
    • Explain that HTML allows a programmer to communicate the way content should be structured on a web page
    • Write a simple HTML document that uses opening and closing tags to structure content
    • Understand how to use lesson resources provided in Web Lab

What to Work On:

What We Plan to Do Next Week:

  • Continue with 2.3: HTML 
  • 2.4: Headings 

Intro to Computer Science- Week of November 18

What We Did:

  • Unit 2: Web Development
  • 2.1: Exploring Websites
    • Identify the reasons someone might visit a given website
    • Identify the reasons someone might create a given website

What to Work On:

  • Unfinished work 
  • All work is due Friday, December 13th 
  • Optional: Code.org- Hour of Code or App Lab

What We Plan to Do Next Week:

  • 2.2: Websites for Expression 

All work due December 13th, 2019

All of the work for the semester is due Friday, December 13th.  If you have any unfinished work or work you'd like to resubmit it must be done by Friday, December 13th. Nothing will be accepted after the deadline for this semester's grades.  Be sure to check Infinite Campus for grades and let me know if you have any questions.  

Week of November 11, 2019: Intro to Computer Science

What We Did:

  • Shared our apps
  • Reflected on input, output, process, and storage for our app

What to Work On:

  • Optional: Code.org, Hour of Code  
  • Optional: make another app! 

What We Plan to Do Next Week:

  • Start Unit 2: Web Development
  • 2.1: Exploring Websites 

Week of November 4: Intro to Computer Science

What We Did:

  • Finished designing our App 
  • Code.Org App Lab 

What to Work On:

  • (optional) Code.Org
    • App Lab- create your own app
    • Hour of Code- practice programming 

What We Plan to Do Next Week:

  • Share our apps with each other
  • Reflect on our app
    • Input, output, process, storage
    • How can we improve our app: define, prepare, try, reflect 

Week of October 28: Intro to Computer Science

What We Did:

  • Kept working in App Lap and designing our app

What to Work On:

  • Code.Org- Hour of Code (optional)
  • App Lab- create a new app (optional)

What We Plan to Do Next Week:

  • Finalize and share our app