Alina: Behavior, Strategy, Implementation/week: 1-3

[AlinaTaoRao]

my fork of the exercises repo: solution-write-ups my fork of the exercises repo: behavior-strategy-implementation group exercises repo: practice-code-review

Study Plan

Learning Objectives

• [x] 🥚 Analyzing Functions: You can analyze a function written at or near your level. This includes:

  • [x] Behavior: How would you document the function, what test cases does it pass, and how might you use it in a program
  • [x] Strategy: Roughly, how could you translate this solution to pseudo-code.
  • [ ] Implementation: What language features were used, and what are some alternate language features that could be used

• [x] 🥚 Testing Existing Functions: You can write unit tests for a working function using the describe/it/expect().toEqual() syntax. This includes grouping test cases into logical test suites.

• [x] 🥚 Function Design: You can explain the function-design process and can successfully apply it to write 2+ solutions matching the behavior of a given function (assuming the behavior is at your level). The solutions do not need to implement different strategies, consider edge cases, or check for invalid arguments.

• [ ] 🥚 Generating Documentation: You can write a correct JSDoc for your functions and use a provided script to generate markdown documentation in a separate file.

• [ ] 🐣 Declarative Programming: You can explain how Declarative Programming is different from Imperative programming, and can tell which paradigm is used in a program. You can also use built-in JS methods to write Declarative solutions to simple coding challenges.

• [x] 🐣 Array Strategies: You can determine which of the primary array strategies (map, filter, reduce, every, some) are helpful for a specific problem at your level.

• [x] 🐣 Higher-Order Functions in Array Methods: You can explain how a higher order function works, and write a callback for use in the primary array methods (for a problem at your level).

• [ ] 🐣 Prototype Delegation: You can inspect a JS value in the browser's debugger/console and explain how to find which methods are available for that value.

• [ ] 🐣 Nested Data: Given a nested data structure containing arrays, objects and primitive values, you can 1) access a given value 2) update a given entry 3) filter the data

• [x] 🐣 Test-Driven Development: You can write basic unit tests for a problem you understand without having a solution to validate your tests. You can use your tests as a guide to develop a solution. You do not need to consider edge cases or invalid arguments.

• [ ] 🐣 Fuzz Testing: You can interpret random test cases for a challenge to guide your development of a solution.

• [x] 🐣 Testing Side-Effects: You can write a suite of unit tests to ensure that; 1) a function does not modify it's reference-type arguments, 2) the function returns a new array/object.

• [ ] 🐣 ECMAScript Modules: You can use export const functionName = () => {}; and import { functionName } from './file-name.js' syntax to separate unit tests from the function definition.

• [ ] 🐣 Continuous Integration: You can check CI scripts locally to ensure your code will pass CI checks when it is pushed, and can read CI results when conducting a code review.

• [ ] 🐣 Code Review: You can use a provided checklist and passing/failing CI checks to review a classmate's function (given the solution is at your level).

• [ ] 🐥 Code Coverage: You can explain what code coverage is, why it's important, and can write unit tests for a code challenge with 100% coverage.

• [ ] 🐥 Testing Edge Cases: You can identify and write unit tests for tricky edge cases.

• [ ] 🐔 Writing Guards: You can write guards for your function parameters that enforce the function's documented parameter types.

• [ ] 🐔 Testing Guards: You can use expect(() => ).toThrow() to unit-test your guards' error type and message.

[AlinaTaoRao]

Week 1

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

Check-In

I Need Help With:

What went well?

What went less well?

• there are a long list of array method, but I just know a few of them, so a lot to learn.
• write and use callback function.

  Lessons Learned

• group work. helps me a lot.

  Sunday Prep Work

[gelilaa]

What went less well?

• there are a long list of array method, but I just know a few of them, so a lot to learn. You can always use MDN docs for reference anytime.
• write and use callback function. Start experimenting with a simple callback functions ,nothing fancy. Once you get hang of it, you can write more complex ones.

[AlinaTaoRao]

@gelilaa

You can always use MDN docs for reference anytime.

Start experimenting with a simple callback functions

Very useful advice. Thanks! 😃

[AlinaTaoRao]

Week 2

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

Check-In

I Need Help With:

1. write unit test with try, catch, toThrow
2. About library, jest. New for me. How deep should I know about it?

   What went well?

What went less well?

Lessons Learned

Sunday Prep Work

[colevandersWands]

write unit test with try, catch, toThrow

These are both 🐔 learning objectives, you don't need to know them. If you have time you can keep studying this but only after you're comfortable with everything else.

About library, jest. New for me. How deep should I know about it?

All you need to know deeply for now is describe, it, and expect(_).toEqual(_). There is the npm command for running tests from VSCode, that uses Jest but you don't need to understand how Jest works. Just how to read the test results

[AlinaTaoRao]

@colevandersWands Thanks for your answer. Now I can confidently focus on those basic but essential exercises. 😄

[AlinaTaoRao]

Week 3

• [ ] I have pushed my progress to:
  • [ ] my fork of the exercises repo: solution-write-ups
  • [ ] my fork of the exercises repo: behavior-strategy-implementation
  • [x] group exercises repo: practice-code-review

Check-In

I Need Help With:

1. I wrote this function as solution to solve sort numbers. For me continue is logical in this function, but when I made PR , Lint-CI throw error: "Unexpected use of continue statement (no-continue)", why? Is this a problem from continue or it's a problem from continue in this function. my PR

const sortNumbers3 = (number = []) => {
  const copyOfNumber = number.map((x) => x);
  // sort the copyOfNumber
  for (let j=1; j<copyOfNumber.length; j++) { 
    let i;
    for(i=0; i<j; i++) {
    // find the one that is larger than copyOfNumber[j]
      if (copyOfNumber[j] < copyOfNumber[i]) {                
         break;
       }
    }

    if(i===j) {continue;} // error: Unexpected use of continue statement (no-continue)

    // insert copyOfNumber[j]
    const temp = copyOfNumber[j];
    for(let k=j-1; k>=i; k--) { // shift one position to right
      copyOfNumber[k+1] = copyOfNumber[k]
    }
    copyOfNumber[i]= temp; // insert copyOfNumber[j]
    }

    return copyOfNumber;
};

What went well?

practice-code-review. I joined a study group and it helps me to adapt to the git workflow.

What went less well?

Read and fix lint: CI errors.

Lessons Learned

Many ways to handle lint-CI error from study group. Save me a lot of time.

Sunday Prep Work

[colevandersWands]

but when I made PR , Lint-CI throw error: "Unexpected use of continue statement (no-continue)", why?

Continue is ok, it must be a configuration option I missed. Linting tools in JS land can get complicated, I'll update this rule in the repo and you can ignore it for now

[AlinaTaoRao]

@colevandersWands Thanks for your answer. 👍