Fenny : Behaviour, Strategy, Implementation, 3 weeks

[FennyWilriani]

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.
• [ ] 🐣 Generating Documentation: You can write a JSDoc comment for your solutions and run a script to generate markdown documentation.
• [ ] 🐣 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.
  • [x] 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.
• [ ] 🐔 Code Coverage: You can explain what code coverage is, why it's important, and can write unit tests with 100% code coverage.

---

[FennyWilriani]

Week 1

---

I Need Help With:

I was missing class last Sunday as I was sick, and I currently catching up with the homework.

What went well?

Learning JS through Edabit challenges. Thank you for introducing us to this platform, it really helps.

Lessons Learned

Attending classes in person during this module for smooth learning process is really necessary.

Sunday Prep Work

Will reading further about function design, once I finished the previous homework and push it on my fork.

[danielhalasz]

let me know if you need any more help after watching the class recording

[FennyWilriani]

Week 2

---

What went well?

I really enjoy the exercise this week, although I haven't got the gist of creating fancy line of unit test for some of the exercises, yet it's really satisfying to be able create solution that passes the test. I'm only able to working on 3 exercises including health care worker - premium and fizz buzz from the repo 😢 but I'll keep practicing more.

Lessons Learned

Watch more tutorials to get an inspiration in writing test or/and solutions for different cases.

Sunday Prep Work

Still need to looking up for the new update/repo 😅

[danielhalasz]

it's great that you enjoy it, that is the most important aspect, do not worry if you can not go through all exercises!! I am curious which video tutorials you have found most helpful in this module.

[FennyWilriani]

Hi @danielhalasz , In order to understanding this module, I actually watching quite bunch of YT tutorial and heaps of google reading, as well practicing in Edabit & Codewars to try understand JS behavior. Some of the YT that I found quite helpful and I like the most is from:

• Programming with Mosh - Object oriented, I really like his video as he can explain the JS technical application with the sample that quite easy to understand.
• whatsdev to learn JS programming such as loop, statement, etc. He quite eloquent in deliver the example and easy to understand. Whenever I need a remainder how to do loops for, while, and if else statement, his channel is a place I go to.
• Ania Kubow - Write unit test for JS, for an example of writing unit test
• Sam Meech-Ward Unit testing in JS for other sample of unit testing writing, he made the test writing looks easy 🤓
• The Coding Train I like how he break each part of JS so it'll not be too much to learn/watch in one go.

I actually watching a lot more channel than I mentioned above, yet those I found most helpful, and I can easily spend 3 full day (approximately 10 hours each day) in a week try to train myself with JS. 😸

[FennyWilriani]

Week 3

Group 5 Practice Code Review

What went well

• Creating group repo & create PR
• Writing the solution and documentation for two of this week's exercises - deep-flatten & intersection. I will continue finishing the whole exercise as I find it quite thrilling to learn each challenge and the application of each different method.
• Missed some of the details on my deep-flatten exercise, yet I guess i still have time to improve it until the end of this week 😄

What went less well?

Slightly confused about what caused the lint failed when I push my PR, as on the VSCode my branch passed any linting. I will definitely gonna have it fixed.

Lessons learned

Communication is not at the best with the current group due to their hectic schedule. I think nagging at teammates is necessary to progress on the project 🤔

Sunday Prep Work

As there's no class this Sunday, I will keep working on the challenges.

[danielhalasz]

Slightly confused about what caused the lint failed when I push my PR, as on the VSCode my branch passed any linting. I will definitely gonna have it fixed.

seems like it just expected to have an empty line after the import statement:

[danielhalasz]

Communication is not at the best with the current group due to their hectic schedule. I think nagging at teammates is necessary to progress on the project 🤔

I will try to contribute to some of the nagging 🙂