Generation TECH - Fall

Weekly Activities Schedule

Week 19 (Jan. 21-24)

Mon: 


PREVIOUS WEEKS


Back to Top of Page

Week 18 (Jan. 13-17)

  • Thurs: Participate in Presentation Creation with Mr. Wright
    • Identify the problem
    • Justify the solution
    • Identify the client
    • Identify the audience
    • Build the presentation struture in a mind map
    • Build the basic presentation in Power Point
    • Work on your projects
    • Hand in feed back form for Seeing Photographically
  • Tues: Review Images
    • Review concepts
    • Participate in activities

Back to Top of Page

Week 17 (Jan. 6-10)

  • Fri: Take Pictures and Learn About Digital Image Information (Meta Data)
    • Learn more about the following concepts
      • Exposure
      • Aperture
      • Depth of Field
      • Shutter Speed
      • Focal Length
      • ISO
    • Define terms above
      • Hint: the definitions are below the camera simulator! <- You're welcome :)
        • Still a little confuse?
      • Experience the SLR Explained CameraSim page
        • Again, you're welcome!
    • Form teams of 3
    • Get a camera
      • Each person takes all 3 pictures
    • Download images to iPhoto on one person's computer
    • Share photos in the class folder
  • Mon: Build Criterion C Schedule

Back to Top of Page

Week 16 (Dec. 16-20)

  • Thurs-Fri: Complete Exercises 3.4 (by yourself) and 3.5 (with your team)
    • For exercise 3.4 Create a blog titled, Famous Computer Failure (5 Points)
      • Review rubric (4 Points)
      • Link to your resource(s) (1 Point)
    • For exercise 3.5 what do we need to consider
      • Each person on the team needs to have 1 idea
    • Share your ideas

Back to Top of Page

Week 15 (Dec. 9-13)

  • Thurs: Continue Software Unit Work
    • Review programming patterns and thought process basics with LightBot
    • Read pages 50-54
    • Review programs and software needed for our projects
    • Identify programs needed for projects

Back to Top of Page

Week 14 (Dec. 2-6)

  • Fri: Draft Criterion B
    • Download Forms Zip File
    • Examine the rubric
    • Read the Sample Entry
    • Title blog post, Criterion B: Analysis
      • Include the following sections:
      • Proposed solution: 
      • Requirement specification
      • IT system requirements
      • System interaction
      • Input/output requirements
        • Input requirements
        • Output requirements
      • Processing
      • Security 
  • Tues: Start Software Unit
    • Take the hardware quiz
    • Read chapter 3 pages 44-46
    • Watch and participate with the software education team operating system (OS) presentation
    • Take the OS quiz
  • Mon: Finish Sharing Computer Orders and Review Project Complexity

Back to Top of Page

Week 13 (Nov. 25-27)

  • Wed: Review Computer Hardware
    • Fill in the Self-Regulation Rubric
    • Fill in the Teacher Feedback Rubric (for the team)
    • Create a blog post title, Computer Hardware
      • Reflect on what you learned by taking a computer apart and putting it back together
      • Include a Creative Commons image
    • Set deadline for Criterion B
      • Start working on Criterion B
  • Tues: Review and Identify Parts
    • Put computer back together
    • Review Criterion B
      • Review Analysis Form
  • Mon: Listen to Guest Speaker, Oscar McNamara, and Review Handout

Back to Top of Page

Week 12 (Nov. 18-22)

  • Thurs: Share Computer Orders and Recommendations
    • Each team present the screenshot of parts and the justification of the parts selection
    • Each individual create a blog post titled, Computer Order
      • Reflect on the process of researching computer parts
      • Include an image, maybe the screenshot of parts
    • Begin computer deconstruction and part identification
  • Wed: Create a Computer Order
    • Form teams
    • Be assigned one of the three scenarios
    • Read the scenario
    • Justify the computer component choices
      • Paragraph explaining your computer component choices
    • Take a screenshot of your order
    • Items to be purchased:
      1. CPU
      2. CPU cooling
      3. Thermal grease (for CPU)
      4. RAM
      5. Power Supply
      6. Motherboard
      7. Storage (Hard drive or Solid State Drive)
      8. Operating System
      9. Graphics Cards
      10. Monitor
      11. Case 
      12. DVD/Blu-Ray drive
      13. Speakers
      14. Mouse
      15. Keyboard
  • Tues: Review Blog Posts and Start Hardware Unit
    • Read pages 30-34
    • Tomorrow your team will create a computer order
    • Thursday your team will take apart and put back together a computer
  • Mon: Finish Team Plan and Publish a Blog Post
    • Title the blog post, How to Assess Teaching?
    • Answer the question: how will I be graded for teaching my chapter?
    • Review Danielson Framework PDF and consider the following assessment options:
      • Domain 3: Instruction
        • 3a Communicating With Students
        • 3b Using Questioning and Discussion Techniques
        • 3c Engaging Students in Learning
        • 3d Using Assessment in Instruction
        • 3e Demonstrating Flexibility and Responsiveness
      • Look at the rubrics for each of the Danielson components
    • Finish editing the class Google document
      • Assign tasks to each team member
      • Build a daily schedule for each day of your chapter
      • Remember everyone needs tasks to fulfill each day of your unit
      • Hardware Team - What is happening each day and assign who's doing what on each day?
      • Software Team - What is happening each day and assign who's doing what on each day?
      • Multimedia Team - What is happening each day and assign who's doing what on each day?
      • Business Team - What is happening each day and assign who's doing what on each day?
      • Database Team - What is happening each day and assign who's doing what on each day?
      • Education Team - What is happening each day?
      • Home & Leisure Team - What is happening each day and assign who's doing what on each day?
        • Home & Leisure team - how long will each presentation be?
        • Can you better define how long each person will present? How many days for each person?
        • Build a simple schedule in the Google document
      • AI Team - Figure out how long your presentation will be?

Back to Top of Page

Week 11 (Nov. 12-15)

  • Wed: Continue Building Units
    • Edit the Google Doc
    • Decide two things
      1. What are we going to read and discuss?
      2. What are we going to do to help students really remember the material?
    • Place this information in the Google Doc
    • Place the exercise numbers in the Google doc, like 2.1
      • Mr. Le Duc will provide your team with resources for the exercises you chose
    • Build year long schedule
    • Review Criterion A requirements
      • Your interview should have already happened
      • You should have a client identified
      • You should have evidence of the interview
      • You should have a problem identified
      • You should have described the current inadequacies of the situation
  • Tues: Work on Unit Structure
    • Assign teams
      • Chapter 1 introduction
        • Mr. Le Duc
      • Chapter 2 Hardware
        • Alec
        • David
        • John
      • Chapter 3 Software
        • Sam
        • Steven
        • Walid
      • Chapter 6 Multimedia
        • Gavin
        • Forrest
        • Connor
      • Chapter 9 Business & Employment
        • Mason
        • Xie
        • Shelby
      • Chapter 8 Databases
        • Sierra
        • Andrew
        • Fernando
      • Chapter 10 Education
        • Davin
        • Rachel
        • Max
      • Chapter 13 Home & Leisure
        • Madeleine
        • Drew
        • Andrew T.
    • Hand out textbooks
    • Start building unit outcomes, activities and the schedule for the year

Back to Top of Page

Week 10 (Nov. 4-8)

  • Thurs: Begin Building The Class Structure
    • Fill in the Chapter Chooser Form
    • Mr. Le Duc will sort the teams
    • Discuss the what, why and how of running a class
      • What were the best processes for:
        • Teaching / presenting
        • Activities
        • Grading - evidence of learning
        • Participation
  • Wed: Finish Blog Post and Discuss Chapters
    • Update on client work and criterion A
    • Finish From Knowledgeable to Knowledge-Able presentation and notes
    • Start hardware projects
  • Mon: Review Interview Tips
    • Once around the room to share progress
      • Criterion A in final form is due at the end of the week
    • Analyze and evaluate OLPC in handout pages 6 through 9

Back to Top of Page

Week 9 (Oct. 28 - Nov. 1)

  • Thurs-Fri: Create Criterion A Blog Post
    • This and your Interview Tips blog post being published on time (by midnight Friday) will be a big part of your Self-Regulation assessment this week
    • Fill in the Self-Regulation Rubric
  • Tues-Wed: Finish Presenting Articles
    • Set deadlines for project
      • Interview and criteria A is due: Friday
    • Review Criterion A
    • Practice interviewing
  • Mon: Assess and Present Articles Blog Posts 
    • Review individual shape and team construction
    • Team up with a partner, assigned by Mr. Le Duc, review and assess blog posts
    • Use the Article Scoring Sheet
    • 22 Points for article blog post
      • Difference between technology and information technology (4 Points)
      • 6 Links (6 x 1 Point) with the following defined (not stated)
        • Stakeholder (6 x 1 Point)
        • Social impact (6 x 1 Point)
        • Ethical issues identified (6 x 1 Point)
    • Example blog posts

Back to Top of Page

Week 8 (Oct. 21-25)

  • Thurs: Defining What is Information Technology?
    • Review Student Self-Regulation Rubric
    • Define what is information technology
      • Input -> Processing -> Output
        • Processing can also result to network and or storage
    • Create a blog post titled, Information Technology Articles
      1. Copy and paste 6 links to articles about InfoTech
      2. Write what a small paragraph explaining the difference bewteen technology and information technology
      3. Identify the 3 elements listed below for EACH article
    • Be prepared to share (Page 6 of handout):
      1. The stakeholders
      2. The social impacts
      3. The ethical issues

Back to Top of Page

Week 7 (Oct. 14-17) 

  • Wed: Brainstorm Project Ideas, Share Scenarios and Review Blog Posts
  • Tues: Review Feedback Forms
    • Pick up your YuGiOh card
    • Take the personality shape survey
    • Examine Feedly.com Reader
      • Review Mr. Le Duc's process for reviewing work
    • Conference with Mr. Le Duc about your My Presentation blog post
    • Remember to email Mr. Le Duc if you want him to review your work
    • Remember to resubmit your feedback form or checksheet, if you want Mr. Le Duc to review your work
    • View Remind 101 Video Overview
      • Remind101 Inc., a safe way for teachers to communicate with students and parents.
      • Text @gentech to (646) 434-0091 or email gentech@mail.remind101.com
      • Standard text message rates apply
      • Visit remind101.com to learn more
      • To opt-out, text 'unsubscribe @gentech' to (646) 434-0091.
    • Form teams of three
    • Participate in a scenario related to the local community. The city council wants to find out about trash disposal in the community in order to clean up the streets.
      • Work in groups of 3 to outline how they would 
        • Approach the problem
          • What kind of data they might need to collect?
          • How they would collect and analyze the data?
      • Making a case vs. discovery
        • Making a case (advocacy)—Use data to document situations that contribute to make a positive or negative case for something. (e.g., Let the Metro know about timing of trains and buses; tell the principal about something that needs to be done at the school; tell someone about something you’d like to see continued.
        • Discovery—Collect data to document situations and then use the data to learn something. (e.g., could your food choices be improved?; do I always take an efficient route to activities?)
          • What research questions might you ask in each case?
          • What is your research question?
          • Why did you choose to collect these data for this question?
          • What are the limits of this data?
          • What can you confidently say based on your data?
          • What perspectives are left out based on your data?