Skip to content

README.md

Latest commit

 

History

History
23 lines (21 loc) · 2.51 KB

README.md

File metadata and controls

23 lines (21 loc) · 2.51 KB

Assessing your JavaScript Fundamentals Fu

  • The objective of this challenge is to get you used to answering a few questions about JavaScript that are commonly asked in interviews.
  • We also have some more reps for you to help hammer in the knowledge you've thus far learned.
  • Answers to your written questions will be recorded in Answers.md
  • This is to be worked on alone but you can use outside resources. You can reference any old code you may have, and the React Documentation, however, please refrain from copying and pasting any of your answers. Try and understand the question and put your responses in your own words. Be as thorough as possible when explaining something.
  • Just a friendly Reminder Don't fret or get anxious about this, this is a no-pressure assessment that is only going to help guide you here in the near future. This is NOT a pass/fail situation.

Start by forking and cloning this repository.

Questions - Self Study - You can exercise your Google-Fu for this and any other Sprint Challenge in the future.

  1. Describe some of the differences between .forEach & .map.
  2. Name five different Types in JavaScript. A Type is something that can represent data. What is so special about Arrays?
  3. What is closure? Can you code out a quick example of a closure?
  4. Describe the four rules of the 'this' keyword. No need to provide examples about it this time :)

Initializing Project - We have set up a testing environment for you using Jest

  • Fork/Clone this project into a directory on your machine.
  • cd into your forked local copy.
  • notice there is a package.json file included. remember that a package.json file is like a map of instructions for when you run npm install
  • run npm install to download all the dependancies you need for this project.
  • run npm run watch to start your tests in watch mode. This command will listen for changes as you work through the problems and save your challenges.js file. As soon as you hit save after writing some changes, the linter will run, and the tests will run as well.
  • As soon as you have a test passing, commit your changes to your fork so we can see an active commit stream.
  • Once you're done with all the tests, push your commits to your fork and submit a Pull-Request

Remember you can use any resources you want to solve these problems, but avoid copying/pasting solutions you've previously written. Also if you don't finish all of the challenges, that's fine! Just do what you can and submit your challenges in the end! HAVE FUN!