Class 01 (Data & Variables)

Class 01: Data and Variables

In the prep work for this lesson, the students learned:

1. How to declare, initialize, and reassign variables
2. The number and string data types and how to convert between them
3. The mathematical operators (+, -, *, /, **, %, ++, --) and order of operations
4. The typeof keyword and how to collect user input with readline-sync

Announcements

• Welcome! First day pep talk
• Lesson 2 prep work should be active by the end of class.

Large Group Time (Instructor)

First Class Reminders

• Use Canvas to access course content.

• Use GitHub for all exercises, studios, and graded assignments.

• Set expectations for students:

  • Part-Time Students

    • Do ALL of the prep work before class.
    • Ask questions often.
    • Make use of the help and resources available.
    • Contact IAs with questions, not the lead instructor

  • Full-Time Students

    • The class design allows for in-class work time.
      • Prep Work time is for reading, concept checks, and working on exercises
      • Work days are for Assignments or catching up on work
    • Ask questions often.
    • Make use of the help and resources available.

• Introduce the IAs and assign groups (may be done during Kickoff prior to the first class).

• Other relevant contact information.

Lesson 1 Topics That Require Careful Attention

1. Cloning repos and committing code. Learners may need some help knowing the difference between forking and cloning a repo, dealing with untracked files, and troubleshooting git error messages
2. Navigating with the terminal. In particular, you may need to remind learners how to use cd to change directories and pwd to see what directory they're in currently and that they can only run their code from the directory that it's in. (This can be especially confusing when they have the right file open in VS Code.) Also where they should be seeing console.log output -- it's in the terminal, not the file they're editing or the browser.
3. let vs. const. When should each be used?
4. Discourage the use of var. If students want to know more technical details as to why we won't be using var, that topic is covered in the chapter on scope.
5. +=, -=, etc. can be used as a shortcut (e.g. num = num + 3 vs. num += 3).
6. Modulus
   1. This is likely a new idea for many of the students. Provide a clear, deliberate explanation (with examples) of what it does.
   2. Why would we need to use %? Don't get too detailed yet, but note some simple scenarios where it might be necessary. The students do not know if/else yet, so keep your explanation non-code specific.
7. Walk through the syntax and how to use readline-sync to collect user input from the console.
   1. Tell them more about what the console is and remind them about where to find it in VS Code.
   2. Live coding examples.
8. The studio is a non-coding activity.
   1. Refer to the TF Notes and prepare a brief intro about why this activity will benefit the students.
9. Part-Time Students: Graded Assignment #1 is open! With each of the six graded assignments in Unit 1, the key is to read through everything carefully and start on what you can do as soon as possible. In class, read through the instructions with your students and highlight what they are capable of doing after this class.
   1. Graded Assignment 1 has been broken into 3 parts.
10. Full-Time Students: Graded Assignment 1 will be introduced and open on Day 5.
11. The attendance code needs to be entered in Canvas exactly as written. You may want to note which learners are present (screenshots are useful if remote) so that you can manually give them credit for attendance if they mistype the attendance code or put it in the wrong place. (Common issues are entering the kickoff attendance code for Class 1 or not matching the capitalization and/or spacing exactly.)

Studio (IA Notes)

Best Practices for ALL Studios

1. Check in with EVERY student during EVERY studio.
   1. This builds relationships and trust, and it helps you spot potential issues before they get too large.
   2. Checking in does NOT mean a quick question like, "How are you doing? Need any help?" Instead, if you are together in person, sit next to the student and ask specific questions about their code, their interpretation of the instructions, or their coding dreams.
   3. Provide detailed feedback as often as possible. "Good job!" does not cut it. An example would be "Hey! I like your variable names! They are very descriptive!".
   4. For virtual studios, rotate between breakout groups in Zoom. It can help to set an interval ahead of time (such as switching rooms every 10 minutes) so you get a chance to look in on everyone
2. Be prepared to clarify the studio instructions beyond just re-reading the words on the screen.
3. Encourage students to work together and share ideas.
4. Assist groups as questions arise. Address frequent mistakes and/or questions to your whole group.
5. Experiment with the size of studio groups, between 2-4 learners, and find what works best for your cohort. (Groups larger than 4 is not recommended, as it's too hard to ensure that everyone participates.)
6. Make a note of any issues that occur during the studio and provide that feedback to the instructor and LaunchCode team.

Lesson 1 Studio

1. Even though this is a non-coding studio, it requires more preparation and thought than usual.
2. The studio helps the students build confidence and identify what they want to get out of this class, so it is critical that you play your part well.
3. Refer to any notes you received from LaunchCode as you prepare for and run the studio as well as the studio guide here.