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.

Instructions

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.

Commits

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.

Description

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.

Self-Study Questions

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 once on each element while map creates a new array of the result of functions run on each element.

2. What is the difference between a function and a method? A function is a block of code that does some task while method is a function used as a property in an Object.

3. What is closure? A closure is when a function has access to variables in its outer or top-level scope.

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

   • The first rule of this is when a function is available in the global scope, the value of this becomes the window object.

   • The second rule of this is when a function is called by a preceding dot, this becomes the object before the preceding dot.

   • The third principle of this keyword is the usage of new keyword when instantiating a constructor function. this becomes the instance of the function.

   • The fourth rule of this is using call(), or apply(), or bind() to explicitly bind this.

5. Why do we need super() in an extended class? super() is needed when extending a class because it is being used to call the methods of the parent class and also to pass the parameters required by the parent class.

Project Set up

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.

Minimum Viable Product

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.

Task 1: Objects and Arrays

Test your knowledge of objects and arrays.

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

Task 2: Functions

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!

Task 3: Prototypes

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

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

Task 4: Classes

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.

Stretch Problems

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