Brian Munene: Behavior, Strategy and Implementation, 3 Weeks

[BrianMunene96]

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 to move on. You do not need to finish all of them but should feel comfortable that you could 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. Remix

Practice studying and remixing other people's solutions to coding challenges. Create your own solutions by mixing and matching pieces from other people's code.

• 🐣 Reconstructing: You can reconstruct a variety of solutions to the same challenge when they are presented as parsons problems.
• 🐣 Analyzing: You can analyze a function written at your level. This includes:
  • [x] Behavior: Write documentation, test cases and use cases to describe the function's behavior.
  • [x] Strategy: Describe the function's strategy using plain english.
  • [x] Implementation: List the language features in a function and explain how each one is used.
  • [x] Small Changes: You can think of 2+ changes to the function's implementation that would not change it's strategy.
• 🐣 Remixing You can analyze several solutions to the same challenge then ...
  • [x] Write: Your own solution by remixing the ones you studied.
  • [x] Explain: How the other solutions inspired yours; what ideas did you take from them? what ideas did you not take?
  • [x] Analyze: Complete a write-up your own solution as though someone else wrote it.

2. Write

• 🐣 Function Design:
  • [x] Writing Tests: Given a working function, you can write passing test cases to describe it's behavior.
  • [x] Writing Functions: You can design multiple solutions to the same code challenge, keeping notes about different experiments you tried along the way.
• [x] 🐣 Generating Documentation: You can write a JSDoc comment for your solutions and run a script to generate markdown documentation.
• [x] 🐣 Fuzz Testing: You write solutions that pass randomly generated test cases.
• 🐥 Test Driven Development: You can solve open-ended, ambiguous coding challenges at your level:
  • [x] Reading Docs: You can understand what the function is supposed to do by reading it's JSDoc description.
  • [x] Writing Tests: You can write test cases before there is a function to test.
  • [x] Writing Functions: You can write one function that passes the test cases you have prepared (even if it's just 1 test case!).
  • [x] Refactoring: You can improve your function's implementation without failing any test cases that were passing.
  • [ ] Iterative Development: You can repeat the TDD process until you are satisfied with your test cases and solution.
• [x] 🐔 Code Golf: Write your solutions with the fewest characters possible! This won't help you write readable code, but it will make you think deeply about JS, your strategy and implementation.

3. Review

• 🐣 Continuous Integration: You can check your code's quality before pushing so your CI checks all pass.
  • [x] Formatting
  • [x] Linting
  • [x] Testing
• [x] 🐣 Code Review: You can use a checklist to give a thorough, positive and constructive review of your classmates' solutions.
• [x] 🐔 Code Coverage: You can explain what code coverage is, why it's important, and can write unit tests with 100% code coverage.

--

[BrianMunene96]

Behavior, Strategy, and Implementation - week 1

• [x] I have pushed my progress to my fork of exercises repo - template write-up

I Need Help With:

• All is well for now

General remarks

• I have really enjoyed learning about unit testing. Initially, I thought it might be a challenging topic but the coaches did an amazing introduction and now I am looking forward to even learning more. When checking job prospects and requirements of full-stack developers, the ability to write testable code appears very often. This gives me even more motivation to keep pushing 💪

Sunday Prep Work

• I am planning to finish all exercises shared in slack and share the progress before Sunday
• I am also revisiting the inside JS - Unit Testing module to retry the examples and exercises

[BrianMunene96]

Week 2

• [ ] I have pushed my progress to [my fork of exercises repo]()

I Need Help With:

• All is well for now

General remarks

• Currently, I am working through the exercises and almost finished with the easy folder. My plan is to finish the easy ones and then attempt both the medium and hard challenges as much as I can before class. I had a challenge with ES-Lint but I have since disabled it on the workspace until I finish the exercises. Other than that. All is well for now.

Sunday Prep Work

• I am planning to finish all easy challenges, then attempt the medium and hard challenges

[BrianMunene96]

Week 3

• [ ] I have pushed my progress to [my fork of exercises repo]()

I Need Help With:

• All is well for now

General remarks

• I am almost done with my exercise for the group assignment given. I plan to finish by tomorrow. I had a challenge with running jest but I was able to solve it with one of the links provided by the coaches and with the help of @johnedelbi

Sunday Prep Work

• Read some documentation on testing and try to solve some random js challenges