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.

.foreach() passes every element as an argument to a function and returns the result of that function. .map() passes every element as an argument, too, but houses the result of the function in a new array, which is then returned at the end of .map().

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

A method is a function that is specific to a class or prototype. It's accessed using the object or class (e.g. Array.prototype.map() or fred.speak()).

3. What is closure?

Ooo closure. Does anyone actually know?

But, seriously, a closure is created with a function definition. I like to think of it as "execution context" or as a "backpack". When the function is defined, it also saves its execution context, such as variables. When the function is invoked, it can access that execution context by pulling a variable out of the backpack and using it. It's kinda trippy because other functions – even, say, the function that created that new function – can't access that execution context, they can't get in the backpack.

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

• When in the global scope, this refers to the window, which is the highest level in the browser. I believe you can think of this as the "default scope" of this.
• When a function is called using a preceeding dot (e.g. person.speak()), this refers to the object to the left of the dot. By using dot notation, you're implicity using a different "scope" for this.
• When creating an object with the new keyword, the this refers to the object being created.
• In contrast to implicitly binding this, you can explicitly bind this using JavaScript's .call(), .apply(), or .bind(). In that case, you actually pass to one of those functions the "scope" you want this to have.

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

When creating subclasses or extended classes in JavaScript, you need to need to copy the properties and methods of the superclass or parent class. You pass the child class's attributes to super() because that runs the attributes through the parent class's constructor(), so you get the inheritance flowing.

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!