Galal: behavior-strategy-implementation, 3 weeks

[galalkoro98]

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 ...
  • [ ] 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:
  • [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.
• [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.
• [ ] 🐔 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.

---

[galalkoro98]

Week 1

I Need Help With:

Yes to undesrtand on this repo folder

What went well?

testing, behavior and implementation strategy

What went less well?

on this repo i do not understand what I have to do with 1-remix folder which is containg many folder and js files.

Lessons Learned

Unit testing, some little change on writen code, analyzing

Sunday Prep Work

[vkoldus]

Hi @galalkoro98, the idea behind remixing is taking a problem as you did before, but not coming up with your own solution from scratch, but first looking at some solutions other people did. This can give you some new ideas about strategies or approaches you maybe haven't considered yourself. At the end, you can try to write your own solution, using some of the ideas you've seen in the other available solutions. This time, tests are given to you so you can try running them against your solution as well.

The repo structure is indeed a bit confusing. I don't know, why the using-error directory is there, I think you can ignore it. If you look into the parsons-problems directory, each subdir is an assignment, a problem. Each problem directory contains a readme and further subdirs with example solutions of the given problem. In the readme, you can find a problem description and a bunch of tests. Ideally, you should be able to understand all of the solutions, how they work. And theb based on them, come up with your own. Then implement the solution and make sure all the given tests pass.

Now of course there's plenty of assignments, I don't know if it's realistic for you to do all of them, but I think doing at least few can help you a lot.

Is that clear? Did I answer your question?

[colevandersWands]

👋 I can maybe help with these questions as well.

using-errors is there because at this stage in past classes, students started trying to write and test functions that throw errors. This folder is meant to be a little guide to this, but like @vkoldus said it's completely optional.

the parsons-problems folder is meant to be opened with study-lenses, then each implementation is presented as a parsons problem in your browser

[galalkoro98]

@vkoldus & @colevandersWands thanks for checking me out, yeah I kind a understood what I have to do i was little bit confused what i have to do?

[galalkoro98]

Week 2

I Need Help With:

yes I have some element concerning me or I am completly ignorant about which is in exercise hard folder I DID SOLVE ONE OF IT

What went well?

easy exercises went well that let met to understand what really testing is

What went less well?

I had not enough time to cover everything

Lessons Learned

I learned a lot even let me to check my array knowldege but I thin need to understand object more

Sunday Prep Work

yes

[galalkoro98]

Week 3

check My-work

I Need Help With:

some errors was quite confused and I asked for help, and I got my answer.

What went well?

Exercise was quite easy just the import and require was little confused.

What went less well?

I think in my side everything went smothely, just the member of group were silncce and no body ask for help, and not push his/her changes.

Lessons Learned

• jason file configuration
• coverage
• JsDoc
• Eslint
• prettire configuration
• another way to ipmort or require file from module.

Sunday Prep Work

I am excited to start with 7. Separation of Concerns