Sprint Challenge: JavaScript Fundamentals

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() executes a function on each element of an array and can be used to mutate the array. Also it will always return undefined. .map() also executes a function on each element of an array. But the difference is that it returns a new array instead of mutating the existing array.

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

Functions are self-contained programs that can be used independently. Whereas, methods are functions defined with reference to the instance of a class i.e. object. Methods can only be used with reference to an object, and not independently.

3. What is closure?

A closure is a function combined with its environment. For example, if we define a function which has a variable and another function inside it, the inside function will have access to that variable defined in the scope of the outer function. That is called closure.

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

Following are the four rules along with brief explanation: Window binding:- this points to browser window when we call it from the window. Implicit binding:- when this is inside of a method function, this will point to the object to which that function is a method. New binding:- this points to the object being created by calling the constructor function with new keyword. Explicit binding:- we can use bind(), call() or apply() methods to get this to point to other objects.

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

In ES6 class syntax, we have super() method which can be used to point the this keyword to the parent class and set the prototype of parent class as the prototype of child class. Its role is to do things which were being done by call() method and Object.create() with respect to prototypical inheritance, before ES6.

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!