This challenge allows you to practice the concepts and techniques learned over the past week and apply them in a survey of problems. This Sprint explored JavaScript Fundamentals. During this Sprint, you studied variables, functions, object literals, arrays, this keyword, prototypes, and class syntax. In your challenge this week, you will demonstrate proficiency by completing a survey of JavaScript problems.

Read these instructions carefully. Understand exactly what is expected before starting this Sprint Challenge.

This is an individual assessment. All work must be your own. Your challenge score is a measure of your ability to work independently using the material covered through this sprint. You need to demonstrate proficiency in the concepts and objectives introduced and practiced in preceding days.

You are not allowed to collaborate during the Sprint Challenge. However, you are encouraged to follow the twenty-minute rule and seek support from your PM and Instructor in your cohort help channel on Slack. Your work reflects your proficiency in JavaScript fundamentals.

You have three hours to complete this challenge. Plan your time accordingly.

Commit your code regularly and meaningfully. This helps both you (in case you ever need to return to old code for any number of reasons) and your project manager.

You will notice there are several JavaScript files being brought into the index.html file. Each of those files contain JavaScript problems you need to solve. If you get stuck on something, skip over it and come back to it later.

In meeting the minimum viable product (MVP) specifications listed below, you should have a console full of correct responses to the problems given.

Demonstrate your understanding of this week's concepts by answering the following free-form questions.

Edit this document to include your answers after each question. Make sure to leave a blank line above and below your answer so it is clear and easy to read by your project manager

1. Describe the biggest difference between .forEach & .map.

the biggest different between .map and .forEach is that .map returns a new array of elements & allows changes on the values by passing each element through a callback function.

2. What is the difference between a function and a method?

methods and functions both act upon the block of code that is enclosed within them since they are both functions. methods act upon a specific object while invoked, while functions do not need an object or receiver to be correctly invoked.

3. What is closure?

closure occurs typically when a function returns another function. within this return, a set of variables that are defined outside of the return function (let's call them closeX) become part of the scope of the return function. This allows for access to that variable (closeX) when the return function is being executed and there is no memory of the initial function in which the variable (closeX) was originally defined in. To sum it up: closure is a collection of all the variables in scope at the time of creation of the function.

4. Describe the four rules of the 'this' keyword.

• window/global object binding: use this without .this or anything. so a simple funciton with 'return this' does it on global. ex. function () { return this; }
  • this will refer to the window/console you are in and return the this of window/console object. output is typically huge.
• implicit binding: 'this.' refers to calling a function with a preceding dot; the this is the object before the dot. ex. 'pri.name' 'name' function will refer back to 'pri' object.
• new binding: using a constructor function, and then creating a new object using 'new' keyword
• explicit binding: when .call & .apply are used. allows for overriding of constructor objects. same as breakout section

5. Why do we need super() in an extended class?

super() is used when creating parent and child classes. when a child class inherits methods from its parent (or in the example of constructor functions, child inherits parent prototype), the use of super() allows for inheritance of parent method without requiring other syntax. it takes care of the binding that we had to do with .call() with constructor functions and prototypes.

Follow these steps to set up and work on your project:

• Create a forked copy of this project.
• Add PM as collaborator on Github.
• Clone your OWN version of Repo (Not Lambda's by mistake!).
• Create a new Branch on the clone: git checkout -b <firstName-lastName>.
• Create a pull request before you start working on the project requirements. You will continuously push your updates throughout the project.
• You are now ready to build this project with your preferred IDE
• Implement the project on your Branch, committing changes regularly.
• Push commits: git push origin <firstName-lastName>.

Follow these steps for completing your project:

• Submit a Pull-Request to merge Branch into master (student's Repo).
• Add your Project Manager as a Reviewer on the Pull-request
• PM then will count the HW as done by merging the branch back into master.

Your finished project must include all of the following requirements:

Pro tip for this challenge: If something seems like it isn't working locally, copy and paste your code up to codepen and take another look at the console.

Test your knowledge of objects and arrays.

• Use the objects-arrays.js link to get started. Read the instructions carefully!

This challenge takes a look at callbacks and closures as well as scope.

• Use the functions.js link to get started. Read the instructions carefully!

Create constructors, bind methods, and create cuboids in this prototypes challenge.

• Use the prototypes.js link to get started. Read the instructions carefully!

Once you have completed the prototypes challenge, it's time to convert all your hard work into classes.

• Use the classes.js link to get started. Read the instructions carefully!

In your solutions, it is essential that you follow best practices and produce clean and professional results. Schedule time to review, refine, and assess your work and perform basic professional polishing including spell-checking and grammar-checking on your work. It is better to submit a challenge that meets MVP than one that attempts too much and does not.

There are a few stretch problems found throughout the files, don't work on them until you are finished with MVP requirements!