Shewit: Behavior, Strategy, Implementation, 3 weeks

[Shewitttt]

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:
  • [ ] Behavior: Write documentation, test cases and use cases to describe the function's behavior.
  • [ ] Strategy: Describe the function's strategy using plain english.
  • [ ] Implementation: List the language features in a function and explain how each one is used.
  • [ ] 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 ...
  • [ ] Write: Your own solution by remixing the ones you studied.
  • [ ] Explain: How the other solutions inspired yours; what ideas did you take from them? what ideas did you not take?
  • [ ] Analyze: Complete a write-up your own solution as though someone else wrote it.

2. Write

• 🐣 Function Design:
  • [ ] Writing Tests: Given a working function, you can write passing test cases to describe it's behavior.
  • [ ] 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:
  • [ ] Reading Docs: You can understand what the function is supposed to do by reading it's JSDoc description.
  • [ ] Writing Tests: You can write test cases before there is a function to test.
  • [ ] Writing Functions: You can write one function that passes the test cases you have prepared (even if it's just 1 test case!).
  • [ ] 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.
• [ ] 🐔 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.
  • [ ] Formatting
  • [ ] Linting
  • [ ] Testing
• [ ] 🐣 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.

---

[Shewitttt]

Week 1

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

I Need Help With:

What went well?

• It was good to try the exercises on edabit.
• first time installing jest/mocha.
• I attempted basic testing for addArray exercise.
• I am reading other students(alumni) tests to get inspiration for cases.

What went less well?

Lessons Learned

Sunday Prep Work

• Finish writing test cases for parsons problems
• Go through function design before upcoming class.

[danielhalasz]

Considering that you have followed the material only through the recording, you did great so far, looking at your fork. Hope you will find some time to do a few more. Have you also installed Mocha?

[Shewitttt]

Thank you Daniel. Indeed I am trying the 'remove exclamation' now. Yes first I installed mocha then when I checked what my other classmates used it is jest so I installed that later on.

[danielhalasz]

you are a pro 🙂

[Shewitttt]

Week 2

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

What went well?

• I am practicing to write tests.
• I attempted to write test and function for the doctor example.
• I am doing the rest of exercises on the function design folder.

Lessons Learned

• Keep on practicing there is not only one way of solving a problem.

Sunday Prep Work

• Practice test cases and function write up
• Go through code review repo

[danielhalasz]

very nice work for the doctor/nurse exercise, even though it was super difficult to follow the class online last week! well done! one more trick that you might have not seen is that Thibault used a for loop in the test, to check for all years of experience..something like this:

describe(solution.name + ': mySolution', () => {
    describe('When the premium is 200', () => {
        for (let i=0; i<10; i++){
            it('Should multiply by x1,2 when she has less than 10 year experience',
                () => {
                    expect((solution({profession: 'nurse', experience: i}, 200))).toBe(240)
            })
        };
        for (let i=10; i<15; i++){
            it('Should multiply by x1,3 when she has 10 or more years of experience',
                () => {
                    expect((solution({profession: 'nurse', experience: i}, 200))).toBe(260)
            });
        }
        for (let i=15; i<20; i++){
            it('Should multiply by x1,5 when she has 15 or more years of experience',
                () => {
                    expect((solution({profession: 'nurse', experience: 15}, 200))).toBe(300)
            });
        }
        for (let i=20; i<60; i++){
            it('Should multiply by x1,7 when she has 20 or more years of experience',
                () => {
                    expect((solution({profession: 'nurse', experience: 20}, 200))).toBe(340)
            });
        }    
        it('Should throw error if premium is above 500',
            () => {
                expect(()=> (solution({profession: 'nurse', experience}, 200))).toThrowError()
        });

    });

[Shewitttt]

Thank you so much Daniel. I will take that in to consideration.

[Shewitttt]

Week 3

• [ ] I am pushing my progress to our Group 2 repomy fork of exercises repo

What went well?

• I am practicing to write functions and tests for the code review exercise
• Got linting errors when pushing my solution but it was good to go back and correct every error.
• I took few days off for break so I'm a bit late to push the homework.

Lessons Learned

• I should keep on practicing even if it feels like I'm not moving forward.

Sunday Prep Work