Elias; Behavior Strategy; 3 WEEKS

[EliasMlopez99]

Learning 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.
  • [x] 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.

[EliasMlopez99]

Week 1

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

I Need Help With:

so far i don't need any help luckily

What went well?

Well i fully understood the point of describing function and writing up possible behavior from the users, i did take my time to do the exercises but i succeed

What went less well?

Well this week i did not have any major problems, just the only thing that annoys me a bit, is closing my codification with )}] you have to be very precise where you place them

Lessons Learned

1. I learned how to remixed and how to write more than two solutions for the same challenge
2. Now i know the way we have to write the solutions
3. I learned how to used edabit and what it offers to developers

Sunday Prep Work

Right now i am doing some challenges in edabit and figuring out how to write other possible solutions to challenges i already did

i want to say for the first time that i really had fun in the javascript class of the past Sunday :)

[danielhalasz]

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

thanks for the links and the creative problemsolving :) the idea originally was that you fork this repo and write up 3 solutions there https://github.com/HackYourFutureBelgium/solution-write-ups

[danielhalasz]

just the only thing that annoys me a bit, is closing my codification with )}] you have to be very precise where you place them

I feel the pain, this can be frustrating. Luckily there are some VSCode extensions that can help.

[danielhalasz]

i want to say for the first time that i really had fun in the javascript class of the past Sunday :)

💟

[danielhalasz]

can you describe what was fun about it?

[EliasMlopez99]

Week 2

I Need Help With:

so far i don't need any help luckily

What went well?

writing up the test and using jest to check if my code passes or not, frankly this time i did not stress cause is just about to put in practice what we've seen so far and a bit of logic

Lessons Learned

• How to use jest
• I learned how to create possible test and how that would be applied in a real life example by the exercise given by thibaut
• i also understood how to inspect js codes with visual studio

Sunday Prep Work

i am still working on the exercise given by thibaut i will include a screenshot down below of what i have so far of my function, still trying to figure out how to throw error in case premium is greater than the established value

thanks again for your feedback and my apologies for being the last

[EliasMlopez99]

@danielhalasz sorry i did not answer , i had fun that day because there was less talking more practice and Thibaut gave us a lot of feedback. If i understand better, i stress less and i can enjoy more coding :)

[danielhalasz]

Is there anything in the screenshot that you wanted to show? It seems to have some interesting lines.. like lines 49, 53, 62, 66... where you use < > & operators.. hope you have fixed that 🙂 and see why that is problematic this way.

[danielhalasz]

i am still working on the exercise given by thibaut i will include a screenshot down below of what i have so far of my function, still trying to figure out how to throw error in case premium is greater than the established value

one way could be to store the calculated bonus in a variable..and then comparing it to max value, before returning it.

[EliasMlopez99]

Week 3 End of the module

Me

i really struggled with the first class cause i was not present i 've been reading the material and the helped me a lot, what i like about this module is that we jumped into the interesting part of it. I know theory is important, however sometimes "testing yourself" is way better than letting other to tell you how "it could be"

What was not clear, where did you get stuck?

i guess really got stuck with the functions, that's something i would really like to discuss with one of the coaches of HYF if possible, like a small zoom, it would be really great if it was thibaut do not get me wrong the other coaches were just fine but i understood more js within this module, than in the past ones.

What was clear, what did you master?

• The concept of writing up cases, something that really shock me was the fact that we create this cases thinking and how "our" users would react to our web page that must be hard, that is why this whole concept of writing tests is very important to avoid bugs or our programs to crash
• I have more confidence writing my function (however i would wish to get some advices from a coach) i know that i should have asked that this past Sunday but i was so overwhelmed with pulling my exercise that i did not think about it

  Where can you still use some help?

  Well as i mention above just some "tips" "advices" creating functions, i know i'm suppose to read how to do them but i consider i find it better if someone with experience show me how to. sometimes i misunderstand the variables and that can be very serious at the moment of writing up test.

  Where can you help others moving forwards?

Any suggestions for future classes?

Well i wish we could have more codification sections instead of long 'blocks' of explanation, i know that this program has been like this for years though with this matters i prefer practical than the theory. Something like "check out this example" "test it" "try it" "see how it works" now it's your turn.

Beforehand thank you for reading my check in @danielhalasz i know that sometimes i seem a bit out of context or lost but i'm trying my best to understand as much as i can, it can be though to study sometimes but i do not care because i enjoy what i learn. Thanks for your patience

[danielhalasz]

I know theory is important, however sometimes "testing yourself" is way better than letting other to tell you how "it could be"

yes, this is also our goal, and that's why there are so many exercises and examples in all the modules and repos, not just this one, but the previous ones too 🙂

[danielhalasz]

i would really like to discuss with one of the coaches of HYF if possible, like a small zoom, it would be really great if it was thibaut do not get me wrong the other coaches were just fine but i understood more js within this module, than in the past ones.

sure, we can ask Thibault, if he can be available for a followup session one day with the class. is there any specific question that you would ask him? what functions did you get stuck on?

[danielhalasz]

Well as i mention above just some "tips" "advices" creating functions, i know i'm suppose to read how to do them but i consider i find it better if someone with experience show me how to.

can you please try to be more specific about the question? what do you mean by creating functions? declaring functions? function syntax? the scope? the content? parameters? it is indeed highly recommended to first look at the suggested study materials..if you dont like articles, there are plenty of videos online in multiple languages..this is how it will be in real life as well working at a company.. and when after putting in the effort, you still dont understand something, then of course you ask for help..

[danielhalasz]

Well i wish we could have more codification sections instead of long 'blocks' of explanation, i know that this program has been like this for years though with this matters i prefer practical than the theory. Something like "check out this example" "test it" "try it" "see how it works" now it's your turn.

well this is exactly what we are doing. showing examples that are harder to grasp on Sunday, starting teamwork/individual work..and keep practicing during the week until the next Sunday session.. if we did even less explanation on Sundays, it would require you to prepare and learn on your own even more..which as you said above, might not be the best for everyone..so there has to be a balance.. it would be great if everyone came prepared with the knowledge and we could just do exercises in class.