Daniel: asynchronous programming, 3 chapters

[denrique-alvarez]

Study Plan

Learning Objectives

• [x] 🥚 You understand the JavaScript Event Loop, and can demonstrate this by using setTimeout and setInterval to schedule simple tasks.
• [x] 🥚 You can explain why Asynchronous Programming is important for programs that have blocking and non-blocking tasks.
• [ ] 🥚 You can explain the basics of the Client/Server model and HTTP requests and can fetch data from RESTful APIs.
• [ ] 🥚 You can convert built-in Node modules from consuming callbacks being promises.
• [ ] 🐣 You can write and run JavaScript for Node.js or for the Browser. Both environments run JavaScript but they have some important differences!
  • [ ] use cases: You can explain some use cases that are unique to each runtime.
  • [ ] built-in APIs: You can list some of the key APIs available in each environment, and why they are not available in the other.
  • [ ] module systems: You can explain the difference between CommonJS Modules in Node.js and ES Modules in the Browser. You can write and use programs written with either system.
• [x] 🐣 You can break down an asynchronous problem into smaller tasks and solve it using promises. This includes identify which tasks depend on each other and which are independent:
  • [x] dependent tasks: The return value from one task is required to start the next task, these must be completed in a specific order - .then
  • [x] independent tasks: These tasks do not use each other's return values, they can be completed at the same time - Promise.all
• [x] 🐣 You can trace, refactor and write code that accesses the file system between these 3 different syntaxes:

1. • [x] Callbacks
2. • [x] Promises
3. • [x] async/await

• [ ] 🐣 You can step through a Node.js command line application using the VSCode debugger.
• [ ] You can write small programs with a Data Access layer that asynchronously uses data stored in different locations:
  • [ ] 🐣 Browser: You can write a small web page that fetches data from a RESTful API and renders it into the DOM.
  • [ ] 🐥 Node: You can write a small CLI program that reads user input from process.argv and reads/writes the file system.

[denrique-alvarez]

Week 21

Practice repo

Check-In

I Need Help With:

Nothing so far. Just taking the time to absorb new concepts and syntax.

What went well?

Advancing through the material steady and solid.

What went less well?

Lessons Learned

A lot of new concepts and syntax: promises, then and catch, executor callbacks...

Sunday Prep Work

Keep going through the material and revisit a couple key concepts.

[denrique-alvarez]

Week 22

Practice repo

Check-In

I Need Help With:

Nothing so far. Just more practice in different contexts.

What went well?

Progressing through the material felt pretty smooth and gradual.

What went less well?

Despite solving the exercises some concepts seem still too abstract.

Lessons Learned

Using promises in different contexts. Promise.all(), sequential vs. parallel execution, more practice with callback functions...

Sunday Prep Work

Keep going through the material and revisit a couple key concepts, again.

[denrique-alvarez]

Week 23

Practice repo

Check-In

I Need Help With:

Nothing so far. This module has been very useful to see everything working together. A lot is more clear now.

What went well?

Seeing the same concepts over and over again really helps me consolidate my understanding.

What went less well?

Still trying to see everything in practical terms as a bigger picture. No rush though.

Lessons Learned

Use of API's, promises, better understanding of rendering and components, lots of new syntax and language features.

Sunday Prep Work

I have done the first reverse-engineering exercise. I will try to finish the next one at least.