This pull request adds an exercise that allows students to view and discuss the difference between synchronous and asynchronous code. This will be a good preview of the next section in the Syllabus for this week - the callstack.
I, too, struggled a little (more) to make it practical. I also have no idea about an activity that could help a student Describe why writing asynchronous code is important when working with the internet. My feeling after looking at the syllabus is that they will be able to do that at the end of the session. I will try to find an example of a page that gets and displays some data (maybe HTTP status code) but displays a loading message or a spinning cursor and look at that as a group.
What does this change?
Module: JS2 Week(s): 3
Description
This pull request adds an exercise that allows students to view and discuss the difference between synchronous and asynchronous code. This will be a good preview of the next section in the Syllabus for this week - the callstack.
I, too, struggled a little (more) to make it practical. I also have no idea about an activity that could help a student
Describe why writing asynchronous code is important when working with the internet. My feeling after looking at the syllabus is that they will be able to do that at the end of the session. I will try to find an example of a page that gets and displays some data (maybe HTTP status code) but displays a loading message or a spinning cursor and look at that as a group.Rendered version
Who needs to know about this?
@ChrisOwen101 @makanti @Abdoulrazack95