aviv - welcome to js - weeks 7-8

[aviv82]

• 🥚 Three Audiences: You can explain how a single file of code is used to communicate with 3 different audiences:
  • [x] Developers: You can explain how code formatting, comments, logs and variable names make it easier (or harder!) for a developer to understand a program.
  • [ ] Computers: You can explain how a computer follows your instructions to store, read and modify data in program memory.
  • [x] Users: You can explain how the computer creates a dynamic user experience by following different executions paths depending on user input.
• 🥚 Listening and Reading:
  • [ ] You can read code out loud, and understand your classmates when they read code to you. You don't need to understand how a program works to master these learning objectives!
  • [ ] Listening You can exactly re-write a program that a classmate has read
  • [ ] Reading You can read a program out loud and guide your classmates to re-write exactly the same code without them seeing the program. (every indentation, semi-colon, comment and spelling must be identical) to you, without seeing the program they are reading.
• 🥚 Static vs. Dynamic Analysis: You can explain and use these two ways of studying a program, each can help you understand different aspects of your code. To help understand this concept, the options panel in Study Lenses is organized into static and dynamic study options:
  • [x] Static: Studying the text in a code file without running it. Some static study methods are creating a flowchart, analyzing variables, filling out a trace table, and drawing on code.
  • [x] Dynamic: Running code and studying the computer's behavior. Some dynamic study methods are running code and reading console logs, using the trace button, and stepping through in the debugger or JS Tutor.
• 🥚 Analyzing Variables: You can list all the variables in a program, and answer these 5 questions for each variable:
  • [x] Where is the variable declared?
  • [x] What is the variable's scope?Is the variable initialized with a value?
  • [x] How many times is it's value used (read) in the program?
  • [x] How many times is the variable assigned a new value?
  • [x] What types are assigned to this variable during the program's execution?
• [ ] 🐣 Imperative Programming: You can explain what the Imperative Programming paradigm is, and can explain how you know the programs in Welcome to JS are Imperative.
• [x] 🐣 Tracing Execution: You can complete a "steps" trace table and correct your table using console output from the "trace" button.
• [x] 🐣 Logging: You can tracing specific aspects of a program's execution and log them to the console.
• [ ] 🐣 Completing Programs: You can successfully fill in blanks for a program when the missing words are provided, including distractors.
• [x] 🐣 Describing Programs: You can read a program and describe it with comments using to the methodology from /describing-programs: zooming out -> zooming in -> connections -> goals
• 🐣 Naming Variables: You can analyze how a variable is used in a program and give it two names:
  • [x] Generic: You can give a generic name to a variable based on how it is used in the program.
  • [x] Specific: You can give a specific name to a variable based on how it's used and the program's domain (the program's specific data and use-case).
• [ ] 🐥 Constructing Programs: You can reconstruct a program's lines and indentation, successfully ignoring distractor lines.
• [ ] 🐥 Modifying Programs: You can make small changes in a program to change it's behavior without breaking it.
• [ ] 🐔 Stepping Through: You can pause a script in a step debugger, arrange the debugger, collapse extra panels, and step through a script written with Just Enough JS. At each point in execution you can make a prediction of the next line before executing, and can check your prediction using the scopes panel.
• [ ] 🐔 Authoring Programs: Given starter code with labeled goals, you can write a small program to match specs (user stories + test cases).

[aviv82]

Week 7

• [x] I have pushed my progress to my practice .js file

Check-In

I Need Help With:

so far so good.

What went well?

created a study plan, and sticking to it. its slow paced. id rather learn 5 things well than 20 without fully understanding anything

What went less well?

no issues so far. there is a lot of stuff to cover and i am pacing myself and documenting my progress

Lessons Learned

• comments
• the console
• variables
• arithmetic properties
• a few built-in objects such as Math
• some b a s i c syntax

Sunday Prep Work

• submit vocabulary pr
• make sure snippet pr goes through
• read, practice, document, rinse repeat :recycle:

[aviv82]

Week 8

• [x] I have pushed my progress to my practice .js file
• [x] i created a repo to practice the skills ive learned

Check-In

I Need Help With:

js in relation to tags, class names and ids. will write a proper issue later today if i cant figure it out myself

What went well?

study plan is more or less on track. i can say i am doing much better this week than the week before

What went less well?

having trouble retaining information. i read one thing and then two things later i forget.

Lessons Learned

• more syntax
• conditions and loops
• eventListener
• querySelector/getElement
• a tiny bit on functions

Sunday Prep Work

• consolidate learning. more practice and repetition until it sticks

[arnochauveau]

js in relation to tags, class names and ids. will write a proper issue later today if i cant figure it out myself

We will focus more on this in the seperation of concerns chapter.

having trouble retaining information. i read one thing and then two things later i forget.

This comes with experience, don't focus too much on remembering syntax. Try to understand how concepts work and Google the syntax when you need it. Don't copy/paste it but type it yourself! This way, you remember it more easily.