Skip to main content


1) Practice the concepts (2 hours)#

This week's concepts can be challenging, therefore let's get an easy introduction using some interactive exercises! Check the following resources out and start practicing.

You can ignore anything to do with XMLHttpRequest

2) Code along (1 hour)#

Now that you've learned about APIs and how to connect with them, let's apply it in the context of a complete application.

In the following application you'll be watching somebody make an API call to an external, public API.

You are welcome to code along as you watch - this will help you to understand what exactly the presenter is doing.


3) JavaScript Exercises (2 hours)#

Here are a set of exercise that will help you to solidify your knowledge of JavaScript.

For this step, open the "Exercises" folder and complete all of the challenges.

Before you start, make sure you fork the repository to your Github account.

4) JavaScript Challenges (6 hours)#

Next, in the same repository complete all of the exercises in the "Challenges" folder.

5) TV Show Project - Part 2/3 (8 hours)#

Continue working on your TV Show Project and so as much as you can.

This could include

  • DOM Manipulation
  • Working with an API
  • Get & Post Requests

Project Details#

All of the details for this project can be found here

5) Give feedback on your colleague's coursework (1 hour)#

Use what you learned in this lesson to give feedback to other trainees who have submitted their coursework.

Helping to give feedback on other peoples coursework doesn't only help them, it also helps you by reading a variety of different code.

You must

View the open Pull Requests here

Find two pull requests from people in your class that have no, or few, comments on them
Leave comments on the two pull requests with improvements or suggestions
Leave a comment saying that you have reviewed it and a nice comment about something you liked (always remember to be nice!)

Make sure you mark at least two other pull requests. It's important that you see a variety of different answers!

Remember, you should use the Code Style Guide to help you