Read these instructions carefully. Understand exactly what is expected before starting this Sprint Challenge.
This challenge allows you to practice the concepts and techniques learned over the past week and apply them in project. This Sprint explored JavaScript Fundamentals. During this Sprint, you studied array methods, this keyword, prototypes, and class syntax. In your challenge this week, you will demonstrate proficiency by completing a survey of JavaScript problems.
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 TL if you need direction.
You have three hours to complete this challenge. Plan your time accordingly.
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.
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 team lead as the evaluate your solution.
Be prepared to demonstrate your understanding of this week's concepts by answering questions on the following topics. You might prepare by writing down your own answers before hand.
-
Briefly compare and contrast
.forEach&.map(2-3 sentences max) -
Explain the difference between a callback and a higher order function.
-
What is closure?
-
Describe the four rules of the 'this' keyword.
-
Why do we need super() in an extended class?
You are expected to be able to answer questions in these areas. Your responses contribute to your Sprint Challenge grade.
- Create a forked copy of this project
- Add your team lead as collaborator on Github
- Clone your OWN version of the repository (Not Lambda's by mistake!)
- Create a new branch: git checkout -b
<firstName-lastName>. - Implement the project on your newly created
<firstName-lastName>branch, committing changes regularly - Push commits: git push origin
<firstName-lastName>
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 advanced array methods and callbacks.
- Use the arrays-callbacks.js link to get started. Read the instructions carefully!
This challenge takes a look at closures as well as scope.
- Use the closure.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!
Follow these steps for completing your project.
- Submit a Pull-Request to merge Branch into master (student's Repo). Please don't merge your own pull request
- Add your team lead as a reviewer on the pull-request
- Your team lead will count the project as complete after receiving your pull-request