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.

A. .forEach will call a callback function on every item in the array but won’t return anything. .map will also call a function on every item in the array but returns a new array of the same size.

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

A. A function is a piece of code that is called by name (e.g. someFunction()). It can be passed data to operate on (i.e. the parameters) and can optionally return data (the return value). A method is a piece of code that is called by a name that is associated with an object (e.g. someObject.someFunction()).

3. What is closure?

A. A closure is the combination of a function enclosed with references to its surrounding state (the lexical environment). A closure gives you access to an outer function’s scope from an inner function.

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

A. 1. Window/Global Object Binding - This is the default binding of this. In this setting, this would refer to the window in a browser or global/console in node. 2. Implicit Binding - The object preceding the dot notation is what this will be bound to. 3. Explicit Binding - Forces a function call to use a particular object for this binding. This is done by using functions such as call, apply, and bind. Call and apply both pass the object as an argument in slightly different ways. Apply passes the object in and any arguments in as an array. Bind creates a copy of the function as a new function and sets this to the object passed in as an argument. 4. New Binding - This binding occurs when calling the function with the new operator. This creates a new empty object that inherits the prototype of the function. Properties and methods are added to the object referenced by this and the newly created object referenced by this is returned implicitly unless another object is returned explicitly.

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

A. The super keyword is used to call the object’s parent constructor to extend the parent class to the child class.

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!