aviv; behaviour, strategy and implementation weeks 13-16

[aviv82]

🥚 Analyzing Functions:

• You can analyze a function written at or near your level. This includes:
  • [x] Behavior: How would you document the function, what test cases does it pass, and how might you use it in a program
  • [x] Strategy: Roughly, how could you translate this solution to pseudo-code.
• [x] Implementation: What language features were used, and what are some alternate language features that could be used 🥚 Testing Existing Functions:
• [x] You can write unit tests for a working function using the describe/it/expect().toEqual() syntax. This includes grouping test cases into logical test suites. 🥚 Function Design:
• [x] You can explain the function-design process and can successfully apply it to write 2+ solutions matching the behaviour of a given function (assuming the behavior is at your level). The solutions do not need to implement different strategies, consider edge cases, or check for invalid arguments. 🥚 Generating Documentation:
• [ ] You can write a correct JSDoc for your functions and use a provided script to generate markdown documentation in a separate file. 🐣 Declarative Programming:
• [x] You can explain how Declarative Programming is different from Imperative programming
• [x] Tell which paradigm is used in a program.
• [ ] Use built-in JS methods to write Declarative solutions to simple coding challenges. 🐣 Array Strategies:
• [x] You can determine which of the primary array strategies (map, filter, reduce, every, some) are helpful for a specific problem at your level. 🐣 Higher-Order Functions in Array Methods:
• [x] You can explain how a higher order function works, and write a callback for use in the primary array methods (for a problem at your level). 🐣 Prototype Delegation:
• [x] You can inspect a JS value in the browser's debugger/console
• [x] Explain how to find which methods are available for that value. 🐣 Nested Data:
  • [x] Given a nested data structure containing arrays, objects and primitive values, you can 1) access a given value 2) update a given entry 3) filter the data 🐣 Test-Driven Development:
• [x] You can write basic unit tests for a problem you understand without having a solution to validate your tests.
• [x] Use your tests as a guide to develop a solution. You do not need to consider edge cases or invalid arguments. 🐣 Fuzz Testing:
• [x] You can interpret random test cases for a challenge to guide your development of a solution. 🐣 Testing Side-Effects:
• You can write a suite of unit tests to ensure that:
  • [x] function does not modify it's reference-type arguments
  • [x] The function returns a new array/object. 🐣 ECMAScript Modules:
• [x] You can use export const functionName = () => {}; and import { functionName } from './file-name.js' syntax to separate unit tests from the function definition. 🐣 Continuous Integration:
• [x] You can check CI scripts locally to ensure your code will pass CI checks when it is pushed
• [x] Read CI results when conducting a code review. 🐣 Code Review:
• [x] You can use a provided checklist and passing/failing CI checks to review a classmate's function (given the solution is at your level). 🐥 Code Coverage:
• [x] You can explain what code coverage is, why it's important
• [x] Write unit tests for a code challenge with 100% coverage. 🐥 Testing Edge Cases:
• [x] You can identify and write unit tests for tricky edge cases. 🐔 Writing Guards:
• [x] You can write guards for your function parameters that enforce the function's documented parameter types. 🐔 Testing Guards:
• [x] You can use expect(() => ).toThrow() to unit-test your guards' error type and message.

[aviv82]

Week 13

Check-In

I Need Help With:

terminology and syntax. the technical vocabulary is expanding but its hard to remember the names of all the new concepts

What went well?

completed a few of the first exercises in study groups. so far most of it is clear.

What went less well?

time management was tough this week. i have dutch exams and a lot of work. hopefully i will have more time to study next week.

Lessons Learned

better understanding of:

• arrays
• functions
• tests

Sunday Prep Work

• keep studying/practicing
• vocabulary
• snippet

[gelilaa]

I Need Help With:

terminology and syntax. the technical vocabulary is expanding but its hard to remember the names of all the new concepts

Remembering everything can be hard. The best way to familiarize with the syntax is to use them and adopt some kind of "Muscle memory"

[aviv82]

I Need Help With:

terminology and syntax. the technical vocabulary is expanding but its hard to remember the names of all the new concepts

Remembering everything can be hard. The best way to familiarize with the syntax is to use them and adopt some kind of "Muscle memory"

thank you Gelila! i am slowly getting there 💫

[aviv82]

Week 14

pushed my progress to practice repo pushed my progress to write-up repo

Check-In

I Need Help With:

prototype delegation, terminology and syntax. specifically methods, high order functions, callback functions, nested functions

What went well?

completed more exercises in study groups, including writing tests for throwing errors and writing guards

What went less well?

prototype delegation went right over my head

Lessons Learned

better understanding of:

• tests
• throwing
• guards
• high order functions
• callback functions

Sunday Prep Work

• keep studying/practicing
• do at least one write-up

[aviv82]

Week 15

pushed my progress to practice repo pushed my progress to write-up repo

Check-In

I Need Help With:

methods, especially methods like forEach or filter that use high order functions

What went well?

completed exercises with group as well as a couple of write ups

What went less well?

i am having a hard time refracting code. there are a few snippets that i am familiar with and comfortable using, but its hard to break away from whats familiar

Lessons Learned

better understanding of:

• methods(but not enough)
• code review workflow
• linting
• debugging
• writing/running tests

Sunday Prep Work

• keep studying/practicing
• make sure snippet and vocabulary prs pass
• finish group work on repo; write readmes, final solutions etc
• write group and module retrospectives

[colevandersWands]

i am having a hard time refracting code. there are a few snippets that i am familiar with and comfortable using, but its hard to break away from whats familiar

This is expected, refactoring and understanding more than one way to do something is very hard. That's why there's a whole module for it! You can't expect to be 100% comfortable with it in 3 weeks, but you've started in the right direction.

You'll get many many more chances to practice these skills in the coming projects. We just introduced the ideas in this module