Callbacks and following the flow of control

Instructions

High level goal for the week

At a high level, this week is about building an effective process for learning unfamiliar language features and patterns. In this workshop, you'll practice one part of this: following the flow of control of code.

Learning objectives

Describe "the flow of control of a program" as "the order in which the parts of the code are executed".
Explain the process you use to follow the flow of control.
Follow the flow of control to help you understand how callbacks work.

Following the flow of control

I want to understand this program's flow of control.

$(document).click(function() {
  console.log("hello!");
});

Before running the code, I add some console.logs. I log 1 in the bit of code I think will get run first, I log 2 in the bit of code I think will get run second, and so on. For example:

console.log(1);

$(document).click(function() {
  console.log(2);
});

console.log(3);

I run the code. If the numbers don't get logged in order (1, 2, 3 etc), I examine the code and try to figure out why. Once I understand, I update my console.logs to reflect the correct order.

Work through the questions (30 mins)

Pair up.
Clone this repo.
Open the index.html file in your web browser.
Open the browser console.
You should see hello!.
Open index.js in your text editor.
Paste the code for question 1 (below) into index.js.
Follow the process outlined in the demo to understand the flow of control of the code in the questions.
Swap driver and navigator. Continue with the next question.

Plenary (15 mins)

We'll come back together for a short plenary to discuss our understanding of following the flow of control.

Questions

Follow the process for understanding the flow of control that we used in the demo.

Question 1

console.log a number in each part of the code. Run the code. The numbers should be logged in order: 1, 2, 3, 4... If they aren't, follow the flow of control to figure out why. Correct the console.logs.

Now fix the code. It should print out the mouse click event object when the mouse is clicked.

var clickEvent;

$(document).click(function(event) {
  clickEvent = event;
});

console.log("Mouse click event object:", clickEvent);

Question 2

$.get("https://async-workshops-api.herokuapp.com/people", function(peopleResponse) {
  console.log(peopleResponse);
});

Question 3

Now fix the code. It should print out the people returned by the API.

var people;

$.get("https://async-workshops-api.herokuapp.com/people", function(peopleResponse) {
  people = peopleResponse;
});

console.log(people);

Question 4

Now fix the code. It should print out the people returned by the API.

function getPeople() {
  return $.get("https://async-workshops-api.herokuapp.com/people", function(peopleResponse) {
    return peopleResponse;
  });
};

console.log(getPeople());

Question 5

This code is incomplete. It should print the names of the people returned by the API. Try and complete it.

function listNamesOfPeople(people) {
  people.forEach(function(person) {
    console.log(person.name);
  });
};

$.get("https://async-workshops-api.herokuapp.com/people");

Question 6

(This code is not broken.)

$.get("https://async-workshops-api.herokuapp.com/people", function(peopleResponse) {
  peopleResponse.forEach(function(person) {
    $.get("https://async-workshops-api.herokuapp.com/people/" + person.id, function(personResponse) {
      console.log(personResponse.favouriteMusic);
    });
  });
});

Question 7

Write code that will console.log alpha after one second, bravo one second later and charlie one second after that. Write the code so that increasing the delay before one console.log will, without changing any other code, increase the delay for the subsequent console.logs by the same amount. For example, if you change the code to print alpha after two seconds, bravo and charlie should automatically be delayed by that extra second, too.

After the workshop

A developer constantly analyses the flow of control of their code. Keep trying to improve this skill.
The more adept you are at reading the flow of control without running the code, the faster you'll be. Build this intuition by making predictions and checking if your prediction is right.
To understand more about callbacks, and to get more practice following the flow of control, complete the questions you didn't have time to do in the workshop.

Resources

Callbacks tutorial

lukew244/callbacks-workshop