A-day AM Agenda
|
Remember, when I check your activities, your conclusions count 30% of your grade. Make sure your answers are worth a whole 30%. Also, if you do not include conclusion answers, you are starting at a 70.
Update 5/14/2020
Anyone sending me a Remind message saying "Hi," "Howdy," or "Hey," will get five points added to their Task #1 grade, since that seems to be the one that most people are not doing well on.
Your last assignment has been added to your curriculum tab. It is CodeHS (big surprise, haha) through Unit Four. Your assignement is due next Thursday, May 21st, with late work due by May 29th.
Anyone sending me a Remind message saying "Hi," "Howdy," or "Hey," will get five points added to their Task #1 grade, since that seems to be the one that most people are not doing well on.
Your last assignment has been added to your curriculum tab. It is CodeHS (big surprise, haha) through Unit Four. Your assignement is due next Thursday, May 21st, with late work due by May 29th.
Update 4/16/2020
Hello, Powdersville!!! How's everyone today? I miss your shining faces and pleasant banter with me. Send me a Remind message just to say hi. I'd love to hear from you.
eLearning....
Ok, campers.... this is what were going to do, I think....at least this is what they tell me we're doing, I think....maybe....
Don't you love indecision? So let's talk about indecision for a second. I know everyone keeps saying these are unprecedented times....yada, yada, yada, but they really are. We all have to be flexible and try to monitor and adjust schedules, expectations, and learning styles to get done what needs to get done.
I feel we have already attained a basic level of instruction needed for an entry level class computer science class. We’ve covered two block-style programming languages, including one that used an graphical user interface (GUI). We’ve also covered two text-based languages. There are particular subjects I would have liked to cover, cybersecurity, more application programming interfaces (APIs), and binary/hexadecimal understanding, that elevate this class to the level of “honors” credit we promised to bring to you, the students. However, in general, I feel good about what we have accomplished.
Here's the important grade part....
According to the District One email, because we are a semester class, students are permitted to better their third quarter grade by four points in order to come up with their semester grade. Therefore, going forward to fourth quarter…..all eLearning tasks will be shifted to fourth quarter as a "satisfactory," "needs improvement," or "missing." Satisfactory will only occur if you have a task grade that is as high or higher than your third quarter grade. Your number grade will still be in your third quarter task list so you can see what your actual percentage is. A grade of "satisfactory" will result in a one percent increase for the semester grade. I changed them all to be “not included in final grade” tasks. That way you will get a sense of the level of completion for each task, but it won’t average anything or change a number in the “grade” column. As each task gets done as "satisfactory," that will be one additional point added to the overall grade for the class.
The first task will be Days 1 and 2 of the eLearning I’ve assigned so far. The second task will be Days 3 and 4 of the eLearning I've assigned so far. If you're done with those tasks and it doesn't give you a grade higher than your third quarter average, message me and I'll discuss with you the possibility of re-taking a CodeHS quiz. Now that we're all quarantined, CodeHS has given be the ability to reset quizzes so you can take them again, but I'm not going to do it without an effort from you. Why should you be worried about it being higher than your third quarter average? Did you read the last paragraph? That is the only way it will positively affect your semester grade.
The third task is posted on my eLearning page, http://lennoncseactc.weebly.com/elearning-a-day-ampm.html. I expect this to take two weeks of my class time allotment in your eLearning situation.
Hello, Powdersville!!! How's everyone today? I miss your shining faces and pleasant banter with me. Send me a Remind message just to say hi. I'd love to hear from you.
eLearning....
Ok, campers.... this is what were going to do, I think....at least this is what they tell me we're doing, I think....maybe....
Don't you love indecision? So let's talk about indecision for a second. I know everyone keeps saying these are unprecedented times....yada, yada, yada, but they really are. We all have to be flexible and try to monitor and adjust schedules, expectations, and learning styles to get done what needs to get done.
I feel we have already attained a basic level of instruction needed for an entry level class computer science class. We’ve covered two block-style programming languages, including one that used an graphical user interface (GUI). We’ve also covered two text-based languages. There are particular subjects I would have liked to cover, cybersecurity, more application programming interfaces (APIs), and binary/hexadecimal understanding, that elevate this class to the level of “honors” credit we promised to bring to you, the students. However, in general, I feel good about what we have accomplished.
Here's the important grade part....
According to the District One email, because we are a semester class, students are permitted to better their third quarter grade by four points in order to come up with their semester grade. Therefore, going forward to fourth quarter…..all eLearning tasks will be shifted to fourth quarter as a "satisfactory," "needs improvement," or "missing." Satisfactory will only occur if you have a task grade that is as high or higher than your third quarter grade. Your number grade will still be in your third quarter task list so you can see what your actual percentage is. A grade of "satisfactory" will result in a one percent increase for the semester grade. I changed them all to be “not included in final grade” tasks. That way you will get a sense of the level of completion for each task, but it won’t average anything or change a number in the “grade” column. As each task gets done as "satisfactory," that will be one additional point added to the overall grade for the class.
The first task will be Days 1 and 2 of the eLearning I’ve assigned so far. The second task will be Days 3 and 4 of the eLearning I've assigned so far. If you're done with those tasks and it doesn't give you a grade higher than your third quarter average, message me and I'll discuss with you the possibility of re-taking a CodeHS quiz. Now that we're all quarantined, CodeHS has given be the ability to reset quizzes so you can take them again, but I'm not going to do it without an effort from you. Why should you be worried about it being higher than your third quarter average? Did you read the last paragraph? That is the only way it will positively affect your semester grade.
The third task is posted on my eLearning page, http://lennoncseactc.weebly.com/elearning-a-day-ampm.html. I expect this to take two weeks of my class time allotment in your eLearning situation.
eLearning, the beginning
eLearning Days 1-4 posted. Click eLearning link in the top right corner.
I will be monitoring email as "office hours" from 10-11:30 and from 1-2:30.
I would prefer you send me Remind texts, and I monitor Remind more than just those three hours.
If you aren't signed up for Remind, please sign up by texting to 81010 the text @actcadayam.
eLearning Days 1-4 posted. Click eLearning link in the top right corner.
I will be monitoring email as "office hours" from 10-11:30 and from 1-2:30.
I would prefer you send me Remind texts, and I monitor Remind more than just those three hours.
If you aren't signed up for Remind, please sign up by texting to 81010 the text @actcadayam.
Day Twenty, March 12th
- Blockly due today and Engineering Notebook due today
- Monday: Quiz on CodeHS concepts through 2.13. This will be a programming quiz worth 55 points. 3/16: Quiz postponed until we reconvene classes.
- We will work on 2.1.2/3 Dead Reckoning today and Monday (after the quiz).
- We'll work on 2.1.2 and the first part of 2.1.3. It is five paths (four from 2.1.2 and one from 2.1.3) for the robot. We will be using V5 Text. You can google help on C++ and use the embedded help in V5 Text.
- I know we didn't get far on this today, but we'll pick back up Monday after the quiz.
- Any time you don't spend on 2.1.2 can be spent on CodeHS. A few people have not even started the last assignment.
Day Nineteen, March 10
If you have completed everything and don't work on something productive (this is not social or gaming hour), I will assign something new to work on.
- Due next class: Notebook, 1.1.4/5 documentation, Blockly documentation
- Blockly
- CodeHS through 2.15
- Robot Maze, coding and documentation
- 1.1.4/5, coding and documentation
- NOTEBOOK!!!
If you have completed everything and don't work on something productive (this is not social or gaming hour), I will assign something new to work on.
Day Eighteen, March 6th
- Your notebooks are due for grading on Thursday, 3/12, for your quarterly notebook grade (20%)
- Activity 2.1.1 Blockly
- This is a block => text code translator
- Use this link instead of the one they suggest: https://blockly-demo.appspot.com/static/demos/code/index.html
- Open a word document. Use "Insert" to print out and document the four programs, both blocks and code.
- You definitely should be able to finish this activity in one day. If you get done early, you may work on CodeHS
- Developer Journal Questions are available on the sign-in table
- I will grade Blockly when you turn in your notebooks next Thursday.
- Don't worry, we'll get back to AppInventor, but I thought we needed a bit more of a break.
Day Sixteen and Seventeen, March 2nd and 4th
A114/5 Due Today (3/2)
CodeHS was due this morning (3/2), so if yours isn't done, it's late anyway. Let's focus on today activity.
A114/5 Due Today (3/2)
CodeHS was due this morning (3/2), so if yours isn't done, it's late anyway. Let's focus on today activity.
- Robot Maze Day
- We'll go over the basics of V5 Blocks and then you will program to complete the course.
Day Fourteen and Fifteen, February 25th and 27th
- Complete 1.1.4 and 1.1.5, document, journal questions for each, Due Monday in class
- Cut off coding time at 10:25
- Print coding to take with you
- Don't forget 114 and 115 journal questions are due Monday
- Cut off coding time at 10:25
- CodeHS - The next endpoint of completion will be 2.15 (Due by 8:00 am on 3/2/20).
- 2/27/20: Amended CodeHS assignment to go through 2.15
eLearning Day on Friday 2/21/20 will require us to flip/flop the day for 114/5 coding and CodeHS work. Therefore the day of CodeHS I'd planned for Tuesday will turn into a 114/5 day. CodeHS can be done outside of class, that's why I assigned it for an eLearning day. Don't leave it to the last minute and then complain that you couldn't access it at home. eLearning assignments are due on Monday, 3/2/20.
Day Twelve and Thirteen, February 19th and 21st
- CodeHS work is now late, but it's still worth doing to improve your grades. Plus, moving forward in CodeHS requires you to know the information.
- Complete 1.1.4 and 1.1.5, document, journal questions for each
- Due Tuesday
- CodeHS - The next endpoint of completion will be 2.17 (Due by 8:00 am on 3/2/20). I'm feeling a CodeHS day on Tuesday? What do you think? On that day we will go over some do's, don'ts, teachable moments and other factoids.
Day Eleven, February 14th
2) Don't have to backspace to clear previous guess
3) Multiplayer horizontal arrangement hides while playing multiplayer secret number is
being used.
4) Horizontal arrangement re-appears when reset button is selected.
5) Secret number is displayed at the end (both for single and for multiplayer)
6) Guess button disappears and guess space is disabled if the player loses
5. The grading rubric is posted at the end of the February 6th agenda.
- All A112/3 Documentation is due.
- CodeHS through 2.11 is due today by 6pm.
- I assume you are finished all of A114. You may continue with A115 (Remember to change file names to reflect the new activity number and add to your Design Overview.).
- Load A114 onto your phone and show it to me. I will be looking for the little things that are enumerated in #3 of today's agenda.
- Some things I am looking for when I check off your app:
2) Don't have to backspace to clear previous guess
3) Multiplayer horizontal arrangement hides while playing multiplayer secret number is
being used.
4) Horizontal arrangement re-appears when reset button is selected.
5) Secret number is displayed at the end (both for single and for multiplayer)
6) Guess button disappears and guess space is disabled if the player loses
5. The grading rubric is posted at the end of the February 6th agenda.
Day Ten, February 12th
- All A1.1.2/3 documentation (including Developer Journal Questions) is due by the beginning of class on Friday, February 14th.
- The next section of CodeHS will be due on Friday, February 14th. All work through 2.11 will be due. You will NOT have time on Friday to work in class.
- First, you will take an A112/3 Quiz. W: drive; A1.1.3 Quiz; password: secret
- The quiz has a 20 minutes time limit.
- Type your whole C1100-### in for your student code, not just the last three numbers.
- You may use your notebooks.
- The rest of today you may work on CodeHS. CodeHS through all 2.11 activities are due Friday by 6 pm.
- However, you may feel like you need to work on other activities from this class.
- If you need to catch up on A112/3 coding or documentation or
- A114 Design Overview, you may do this.
- No other A114 work should be done.
Day Nine, February10th
2) Don't have to backspace to clear previous guess
3) Multiplayer horizontal arrangement hides while playing multiplayer secret number is
being used.
4) Horizontal arrangement re-appears when reset button is selected.
5) Secret number is displayed at the end (both for single and for multiplayer)
6) Guess button disappears and guess space is disabled if the player loses
5. The grading rubric is posted at the end of the February 6th agenda.
- All A112/3 Documentation and journal questions will be graded on Friday, February 14th.
- Continue working on A1.1.4 with your programming pair. If your partner is absent, continue on your own. Do not shuffle partners.
- Pair Programming Timing: Ryan will time 10 minute intervals for you use to switch. Remember you need to stand up and switch seats. If Ryan is absent, Adam D will time for you.
- You should finish all of A114. You may continue with A115 (Remember to change file names to reflect the new activity number and add to your Design Overview.).
- Some things I am looking for when I check off your app:
2) Don't have to backspace to clear previous guess
3) Multiplayer horizontal arrangement hides while playing multiplayer secret number is
being used.
4) Horizontal arrangement re-appears when reset button is selected.
5) Secret number is displayed at the end (both for single and for multiplayer)
6) Guess button disappears and guess space is disabled if the player loses
5. The grading rubric is posted at the end of the February 6th agenda.
Day Eight, February 6th
b. show Mrs. Lennon your working app
c. You should have your Developer Journal Questions done already
d. go through A112 and A113 and make sure you have any vocabulary words you're not familiar
with written out in your notebook so you can use that during the quiz.
You have until 9:15 to finish coding, debug and print documentation for A112/3.
2. We will be doing 1.1.4 next. If you are ready to begin, you may start with the design overview.
Please do not go beyond the design overview because we will be going forward using pair
programming.
3. If you are done with all work, you may continue with CodeHS.
4. Before you begin A114 - Global vs Local Variable and Pair Programming roles
5. A1.1.4 pointers...
a. Design Overview:
1) use your Initial Backlog as checklist
2) if your initial backlog is not a checklist, re-write it
3) Filling Viewer screen first? - this should be on your checklist
b. Renaming components - don't forget
c. Remember how to use Horizontal Arrangement? - Fill Parent
d. Some things I am looking for when I check off your app:
1) Don't have to backspace over words to enter numbers
2) Don't have to backspace to clear previous guess
3) Multiplayer horizontal arrangement hides while playing multiplayer secret number is
being used.
4) Horizontal arrangement re-appears when reset button is selected.
5) Secret number is displayed at the end (both for single and for multiplayer)
6) Guess button disappears and guess space is disabled if the player loses
e. Document..... Coding, Viewer, File list, Document Overview, Journal Questions
A114 Grading Rubric:
- When done with A113, you will need to.
b. show Mrs. Lennon your working app
c. You should have your Developer Journal Questions done already
d. go through A112 and A113 and make sure you have any vocabulary words you're not familiar
with written out in your notebook so you can use that during the quiz.
You have until 9:15 to finish coding, debug and print documentation for A112/3.
2. We will be doing 1.1.4 next. If you are ready to begin, you may start with the design overview.
Please do not go beyond the design overview because we will be going forward using pair
programming.
3. If you are done with all work, you may continue with CodeHS.
4. Before you begin A114 - Global vs Local Variable and Pair Programming roles
5. A1.1.4 pointers...
a. Design Overview:
1) use your Initial Backlog as checklist
2) if your initial backlog is not a checklist, re-write it
3) Filling Viewer screen first? - this should be on your checklist
b. Renaming components - don't forget
c. Remember how to use Horizontal Arrangement? - Fill Parent
d. Some things I am looking for when I check off your app:
1) Don't have to backspace over words to enter numbers
2) Don't have to backspace to clear previous guess
3) Multiplayer horizontal arrangement hides while playing multiplayer secret number is
being used.
4) Horizontal arrangement re-appears when reset button is selected.
5) Secret number is displayed at the end (both for single and for multiplayer)
6) Guess button disappears and guess space is disabled if the player loses
e. Document..... Coding, Viewer, File list, Document Overview, Journal Questions
A114 Grading Rubric:
Day Seven, February 4th
b. show Mrs. Lennon your working app
c. complete the Developer Journal Questions
d. go through A112 and A113 and make sure you have any vocabulary words you're not familiar
with written out in your notebook so you can use that during the quiz.
e. journal questions will be graded Thursday, February 6th.
f. you will have a short time on Thursday to work on A113
We will be doing 1.1.4 next. If you are ready to begin, you may start with the design overview.
If you are done with all work, you may continue with CodeHS.
- A1.1.2/3 journal questions are due by the beginning of class on Thursday, February 6th.
- The next section of CodeHS will be due on Friday, February 14th. All work through 2.11 will be due, however, you will have one whole day on Wednesday, February 12th in class to work on it.
- A1.1.3 starts where A1.1.2 leaves off. When you've completed A1.1.2, you may move on to A1.1.3 by writing out the Design Overview.
- When done with A113, you will need to...
b. show Mrs. Lennon your working app
c. complete the Developer Journal Questions
d. go through A112 and A113 and make sure you have any vocabulary words you're not familiar
with written out in your notebook so you can use that during the quiz.
e. journal questions will be graded Thursday, February 6th.
f. you will have a short time on Thursday to work on A113
We will be doing 1.1.4 next. If you are ready to begin, you may start with the design overview.
If you are done with all work, you may continue with CodeHS.
Day Six, January 31st
Documentation and Developer Journal Questions for A1.1.1 and CodeHS (through 2.3.6) are due today.
1. Discussion about abstraction
2. Downloading AppInventor files to your P: drive
3. A1.1.2 Happy Accelerometer - This activity leads straight into A1.1.3, so there will not be separate
grading for A1.1.2 and therefore not a separate set of journal questions. I would like to see everyone
complete to the end of A1.1.2 by the end of class.
We need to go over.....
a. Extracting from a zipped file/folder
b. Write out your Design Overview
c. Renaming components correctly
4. A111 Quiz after snack time
This is the rubric for A1.1.2/1.1.3:
Documentation and Developer Journal Questions for A1.1.1 and CodeHS (through 2.3.6) are due today.
1. Discussion about abstraction
2. Downloading AppInventor files to your P: drive
3. A1.1.2 Happy Accelerometer - This activity leads straight into A1.1.3, so there will not be separate
grading for A1.1.2 and therefore not a separate set of journal questions. I would like to see everyone
complete to the end of A1.1.2 by the end of class.
We need to go over.....
a. Extracting from a zipped file/folder
b. Write out your Design Overview
c. Renaming components correctly
4. A111 Quiz after snack time
This is the rubric for A1.1.2/1.1.3:
Day Five, January 29th
Documentation and Developer Journal Questions for A1.1.1 are due on Friday, January 31st. CodeHS through 2.3.6 is also due Friday.
Log in to my.PLTW.org, and AppInventor.
Work on Activity 1.1.1 Digital Doodle
a. You need to get at least Challenge A done to get a 95%. Completing Challenge B & C
will give you the possibility of 100%.
b. You will only have until snack time to work on A1.1.1, including printing out the documentation.
c. Leave journal questions until last, so you can make sure you get everything printed you need.
d. Look back through the activity and see if there are any notes you should take. Think about it in
terms of a quiz; think....if Mrs. Lennon asked me a question on this, would I understand it?
Documentation and Developer Journal Questions for A1.1.1 are due on Friday, January 31st. CodeHS through 2.3.6 is also due Friday.
Log in to my.PLTW.org, and AppInventor.
Work on Activity 1.1.1 Digital Doodle
a. You need to get at least Challenge A done to get a 95%. Completing Challenge B & C
will give you the possibility of 100%.
b. You will only have until snack time to work on A1.1.1, including printing out the documentation.
c. Leave journal questions until last, so you can make sure you get everything printed you need.
d. Look back through the activity and see if there are any notes you should take. Think about it in
terms of a quiz; think....if Mrs. Lennon asked me a question on this, would I understand it?
Reminders for documentation:
a. Save coding as a .png (right click in white space of "Blocks"). Open Word, change layout to
landscape, type your name at the top of the page. From "Downloads" folder, highlight the
.png file that has your coding. While it's highlighted, select "Ctrl C." Go to your Word document.
Hit "Enter" after your name. Select "Ctrl V." Your coding should show up. Print this page.
(C1100 printer) Cut and tape into your engineering notebook. Remember all of the correct
things to do with inserts. After they're are properly inserted in your notebook, annotate the Event
Handlers and any other vocabulary (color channels? transparency?)
b. Open a new Word document. Type your name at the top of the page. Use "Insert," "Screen
Shot," "Screen Clipping" to cut and paste the "Viewer" and "Components" of the Designer
screen into the Word document.
c. Open a new Word document. Type your name at the top of the page. Use "Insert," "Screen
Shot," "Screen Clipping" to cut and paste the "Name" and "Date Created" columns of MyProjects
into the Word document.
d. Answer Developer Journal Questions (you may tape in on left side and answer on right side).
These will be your conclusions questions for this activity, so make sure you answer with enough
information that you will get full credit.
a. Save coding as a .png (right click in white space of "Blocks"). Open Word, change layout to
landscape, type your name at the top of the page. From "Downloads" folder, highlight the
.png file that has your coding. While it's highlighted, select "Ctrl C." Go to your Word document.
Hit "Enter" after your name. Select "Ctrl V." Your coding should show up. Print this page.
(C1100 printer) Cut and tape into your engineering notebook. Remember all of the correct
things to do with inserts. After they're are properly inserted in your notebook, annotate the Event
Handlers and any other vocabulary (color channels? transparency?)
b. Open a new Word document. Type your name at the top of the page. Use "Insert," "Screen
Shot," "Screen Clipping" to cut and paste the "Viewer" and "Components" of the Designer
screen into the Word document.
c. Open a new Word document. Type your name at the top of the page. Use "Insert," "Screen
Shot," "Screen Clipping" to cut and paste the "Name" and "Date Created" columns of MyProjects
into the Word document.
d. Answer Developer Journal Questions (you may tape in on left side and answer on right side).
These will be your conclusions questions for this activity, so make sure you answer with enough
information that you will get full credit.
Day Four, January 27th
CodeHS work needs to be completed through the 2.3 activities by Friday, 1/31/2020. This means the activities should be done, including 2.3.6, when you arrive in class. There will be no class time on Friday, 1/31 devoted to CodeHS work.
Beginning:
Work on Activity 1.1.1 Digital Doodle (begin and finish)
- Quick tour around App Inventor
- Log in to App Inventor
- Enter the Design Overview into your Engineering Note
- Split your screen so you have 2/3 App Inventor and 1/3 PLTW
- You need to get at least Challenge A done to get a 95%. Completing Challenge B & C
will give you the possibility of 100%.
Rubric for A1.1.1 Grading:
CodeHS work needs to be completed through the 2.3 activities by Friday, 1/31/2020. This means the activities should be done, including 2.3.6, when you arrive in class. There will be no class time on Friday, 1/31 devoted to CodeHS work.
Beginning:
- Sign in
- Take out pen; Stow backpack under your assigned table.
- Bring pen and notebook to your computer seats.
- Log in to your computer, AppInventor and my.PLTW.org (bring up Activity1.1.1)
- We need to look up registration payments for everyone to see who needs to ask parents for 2nd semester fees.
- While you are waiting, what could you be doing? (Hmmmmm, I think CodeHS is a good answer.)
Work on Activity 1.1.1 Digital Doodle (begin and finish)
- Quick tour around App Inventor
- Log in to App Inventor
- Enter the Design Overview into your Engineering Note
- Split your screen so you have 2/3 App Inventor and 1/3 PLTW
- You need to get at least Challenge A done to get a 95%. Completing Challenge B & C
will give you the possibility of 100%.
Rubric for A1.1.1 Grading:
Day Three, January 23rd
Beginning:
Summarize course units.
- Select the unit, then the unit "Landing Page"
- Read through the Prefaces for all of the lessons for that unit and come up with ONE 30-40
word summary of what that unit will be covering.
- If you finish before others do, work on CodeHS
Summarize Collaborative Strategies
Beginning:
- Sign in
- Take out pen; Stow backpack under your assigned table.
- Bring pen and notebook to your computer seats.
- Log in to your computer
- Log in to CodeHS
- Log in to my.PLTW.org
Summarize course units.
- Select the unit, then the unit "Landing Page"
- Read through the Prefaces for all of the lessons for that unit and come up with ONE 30-40
word summary of what that unit will be covering.
- If you finish before others do, work on CodeHS
Summarize Collaborative Strategies
Day Two, January 21st
- Syllabus
- Engineering notebook introduction
- ERS and Notebook rubrics - practice using engineering notebook
- Phone/Breaktime policy- practice using engineering notebook
- Quick tour of the course
- Learn activity navigation within PLTW
- Log in to my.PLTW.org and finish summary of course units
- Sign up for MIT App Inventor
Day One: January 15th
GREAT first day! We got a lot done, even though we didn't have our whole class time.
1. Scavenger Hunt
2. Name tags - rubric activity
3. Welcome letter
- Please return with a signature
- Remind sign up
4. Computer registration for username
5. Learn how to troubleshoot our own computer issues
6. Sign up for CodeHS - https://codehs.com/go/44E62
GREAT first day! We got a lot done, even though we didn't have our whole class time.
1. Scavenger Hunt
2. Name tags - rubric activity
3. Welcome letter
- Please return with a signature
- Remind sign up
4. Computer registration for username
5. Learn how to troubleshoot our own computer issues
6. Sign up for CodeHS - https://codehs.com/go/44E62
Notebook Documentation
Notes: Engineering Notebook
2 Rubrics (EN and ERS)
Phone Policy
Breaktime Policy
Unit Summaries
Collaborative Strategies
A1.1.1
Notes: Engineering Notebook
2 Rubrics (EN and ERS)
Phone Policy
Breaktime Policy
Unit Summaries
Collaborative Strategies
A1.1.1
- Design Overview
- Design View
- MyProject page of files and creation date
- coding/annotations
- Journal Questions