zerubabel: Welcome to javascript, 3 weeks

[zerubabel4]

Learning Objectives

Priorities: 🥚, 🐣, 🐥, 🐔 (click to learn more)

There is a lot to learn in this repository. If you can't master all the material at once, that's expected! Anything you don't master now will always be waiting for you to review when you need it. These 4 emoji's will help you prioritize your study time and to measure your progress:

• 🥚: Understanding this material is required, it covers the base skills you'll need for this module and the next. You do not need to finish all of them but should feel comfortable that you could do them with enough time.
• 🐣: You have started all of these exercises and feel you could complete them all if you just had more time. It may not be easy for you but with effort you can make it through.
• 🐥: You have studied the examples and started some exercises if you had time. You should have a big-picture understanding of these concepts/skills, but may not be confident completing the exercises.
• 🐔: These concepts or skills are not necessary but are related to this module. If you are finished with 🥚, 🐣 and 🐥 you can use the 🐔 exercises to push yourself without getting distracted from the module's main objectives.

---

1. What is Programming

What is a program? What is a programming language? How do programs and people fit together?

• [x] 🥚 Data in, Data Out: You understand that computer programs are used to transform data, and can explain a JS program from this module in terms of the data that goes in and the data that comes out.
• 🥚 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.
  • [x] 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.
• [x] 🥚 Tracing Variables: You can complete a trace table for a program that uses only variables, and can check your work using the "trace" button.
• 🥚 JavaScript Syntax: Given a program, you can identify these parts of JavaScript syntax:
  • [x] Primitives
  • [x] Operators
  • [x] Identifiers
  • [x] Keywords
  • [x] Checks
  • [x] Blocks
  • [x] Function Calls
• [ ] 🥚 Pseudo Code: You can explain what pseudo code is, how it's used and why it's helpful.
• [ ] 🥚 Program Goals: You understand that a full JavaScript program can be explained as a series of smaller goals, and can write names for the goals in a simple working program.
• 🐣 Program Analysis: You can study a simple working program and identify:
  • [ ] The program's behavior (data in, data out)
  • [ ] The program's goals
  • [ ] The program's syntax and language features
  • [ ] Which parts of the source code are for which audience (users, devs, computers)
• [ ] 🐥 Same Behavior, Different Code: You can study simple programs with the same behavior (data in, data out) but different source code and explain how the differences matter for each audience.

2. Just Enough JavaScript

Go in depth on JavaScript you need to know for writing interactive text-based programs in the browser. Along the way you will learn how each language feature works in small programs.

• 🥚 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 in their program must be identical to yours.
• 🥚 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:
  • [ ] 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.
  • [ ] 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.
• [x] 🥚 Tracing Execution: You can complete a "steps" trace table for all JS language features in Just Enough JavaScript, and can correct your table using console output from the "trace" button.
• [x] 🥚 Analyzing Variables: You can list all the variables in a program, and answer these 5 questions for each variable:
  • Where is the variable declared?
  • What is the variable's scope?
  • Is the variable initialized with a value?
  • How many times is its value used (read) in the program?
  • How many times is the variable assigned a new value?
  • What types are assigned to this variable during the program's execution?
• [ ] 🥚 Completing Programs: You can successfully fill in blanks for a program when the missing words are provided, including distractors.
• [ ] 🐣 Translating Pseudo Code: Given a program written in Pseudo Code, you can translate it to working JavaScript.
• [ ] 🐣 Comparing Programs: You can compare two programs with similar code and explain if they have the same behavior or not. If they do not, you can explain how they behave differently and why.
• [ ] 🐥 Constructing Programs: You can reconstruct a program's lines and indentation, successfully ignoring distractor lines.
• [ ] 🐥 Linting: You can find and fix simple linting errors in JavaScript programs.
• [ ] 🐔 Writing Programs: You can write small programs that log specific values, or pass specific test cases.

3. Understanding Programs

Learn how to understand a larger programs by finding connections between the details and the big picture. By the end of this chapter you will know how to read a new program and do a simple code review.

• [ ] 🥚 Stepping Through: You can pause a script in a your browser's 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.
• [ ] 🥚 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.
• [ ] 🥚 Logging: You can tracing specific aspects of a program's execution and log them to the console.
• [x] 🐣 Naming Variables: You can analyze how a variable is used in a program and give it two names:
  • Generic: You can give a generic name to a variable based on how it is used in the program.
  • 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).
• [ ] 🐣 Describing Programs: You can read a program and describe it with comments using to the methodology from /describing-programs:
  1. Zoom Out
  2. Zoom In
  3. Find Connections
  4. Describe Goals
• [ ] 🐥 Code Review: Given a working program you can review the code for clarity, correctness and style.

[zerubabel4]

I Need Help With:

nothing, thank you

What went well?

• variables
• commenting and logging
• JS Syntax

What went less well?

it's a little more than I expected and it takes time to understand what you doing even while your watching videos.

Sunday Prep Work

i will finish just enough syntax today then i'm trying to finish what is programing, I was working a lot this week so i wasn't active enough.

[colevandersWands]

and it takes time to understand what you doing even while your watching videos.

could we make the videos more helpful, or provide something else as well?

[zerubabel4]

no no thank you it's just my problem I take some time to understand things that's why, thank you.

[zerubabel4]

I Need Help With

What went well?

• devtools debugger
• writing and reviewing
• [computers and developers
• just enough javascript 1-9

What went less well?

Sunday Prep Work

[zerubabel4]

I Need Help With

What went well?

• debugging!
• last week's exercise but the second one was a little hard.
• trying to finish just-enough-javascript until tomorrow.
• finished UX/UI review.
• coding our website with @alexanderism55 so we can't forget HTML & CSS.

What went less well?

Sunday Prep Work

[danielhalasz]

• coding our website with @alexanderism55 so we can't forget HTML & CSS.

💪