sannesofie
commented
2 years ago - [x] 🥚 Stepping Through: You can pause a script in a step debugger (breakpoints and debugger statement), 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.
- [x] 🥚 Assertion Testing: You are familiar with assertions and can use console.assert to guide your study of a program.
- [x] 🥚 Linting: You can find and fix linting errors in JavaScript programs.
- [x] 🥚 Naming Variables: You can analyze a program's variables using a structured comment, and can rename the variables. You can give each variable two different names:
- [ ] Generic: A name that describes the variable's role in a general way. This includes deciding whether to use let or const.
- [x] Specific: A name that fits the variable's role and contextualizes it in the program's domain.
- [ ] 🥚 Program Life Cycle: You can explain the two phases of a program's life cycle.
- [x] 🥚 Fixing Errors: You can use the structured comment to describe an error in your program, and can make several educated guesses at how to fix the error.
- [x] 🥚 Documenting Functions: You can demonstrate your understanding of arguments, parameters and return values by writing a JSDoc comment.
- [ ] 🐣 Explicit Coercion: You is aware of the rules for casting explicitly between types and can complete assertions to describe what value will result, they can have access to the internet and a console.
- [ ] 🐣 Implicit Coercion: You is aware that operators will implicitly cast it's operands to the same type before operating. They can look or experimentally discover the rules for an operator.
- [ ] 🐣 Statements vs. Expressions: You can explain the difference between a statement and an expression, and can identify them in a program. This will be very helpful for understanding how the debugger steps, and for ...
- [ ] 🐣 Operator Precedence: You can refactor an expression with several operators into several statements assigning each step of the expression to a new variable according to the languages rules of operator precedence.111
- [ ] 🐣 Fixing Bugs: You can use the structured comment to describe and fix a bug in small programs.
- [ ] 🐣 Reference vs. Value: You can explain how to swap references or values between variables, explain deep vs. strict equality, and compare two objects or arrays.
- [ ] 🐣 Procedural Programming: You can tell whether or not a JS program is Procedural and can explain how you made your decision.
- [ ] 🐣 Side-Effects: Given a function that takes an array as an argument you can determine if the function has any side-effects, and can suggest a way to avoid the side-effect.
- [ ] 🐣 Debugging Functions: You can read input/output assertion tests to understand a function's actual vs. expected behavior, and to correct the function's behavior.
- [ ] 🐥 Sub-Goal Authoring: Given most of a small program with missing goal, you can write code to implement the missing behavior.
- [ ] 🐥 Hoisting: You can find hoisted functions and variables in the browser's debugger and explain how hoisting is related to program life-cycle.
- [x] 🐔 Refactoring Functions: You can refactor a designated chunk of a program into an empty function body and pass the given assertion tests.
- [ ] 🐔 Reverse-Engineering: You can write a small program from scratch that matches the behavior of an example program.
arnochauveau
gelilaa