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 doesn't create a new array or assign values by itself, where as .map creates a new array and assigns each element to returned value of the callback with the array element as a parameter.

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

A: A function works independently of any parent objects and usually only acts on the parameters passed to it. A method on the other hand is a function that is a member of (or otherwise associated with) an object, used to perform actions related to and or on the object it is a member of. In other words, a method provides functionallity to an object and a function provides generalised functionallity.

3. What is closure?

A: a closure is when an inner function is allowed access to the outer scope it's defined in. It provides a method of 'remembering' variables in it's enclosed scope even when that scope and it's variables are closed.

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

A: The first rule is Implicit binding. This is where 'this' is binded to the object the function is currently being called from. The second rule is 'new' binding. This is when the keyword 'new' is used to create a new object. In this instance, this refers to an empty object that is an instance of the object currently being created. the third rule is global object binding. This is similar to implicit binding, but instead the object 'this' refers to is the global object ('window' for browsers). This usually happens when a function is called independant of any objects. the last rule is explicit binding. This is when 'this' is binded to an object defined explicity. This can be done using methods such as Function.prototype.call(), where the function is invoked and binded to the object passed into the '.call' method.

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

A: super() refers to the parent (or super class) constructor. We need it in order to construct the parent object and apply all of its properties and methods the class we are currently constructing, otherwise extended the parent class becomes largely useless.

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!