henriqueinonhe

4 ms·

1.
Images Are (Probably) Oversized(reasonunderpressure.com)
1 points by henriqueinonhe 1y ago|0 comments
2.
Dare to Experiment(blog.codeminer42.com)
2 points by henriqueinonhe 2y ago|0 comments
3.
React 19 almost made the internet slower(blog.codeminer42.com)
202 points by henriqueinonhe 2y ago|284 comments
4.
Working Effectively with a Headless CMS in React(blog.codeminer42.com)
2 points by henriqueinonhe 3y ago|0 comments
5.
The Essence of Abstraction(reasonunderpressure.com)
1 points by henriqueinonhe 3y ago|1 comments
6.
by henriqueinonhe 3y ago
A deep dive in one of the most important concepts in software development, with a hint of mathetmatics and logic.
7.
by henriqueinonhe 3y ago
Do you still have it?
8.
by henriqueinonhe 3y ago
I'd like to know why the writing "feels off" for you, I'm definitely willing to improve it. If it makes you feel more comfortable, you may DM me here or any other social network (e.g. Github).
9.
by henriqueinonhe 3y ago
Very well said. Complementing your answer, I'd also like to point out that another notable guarantee that promises give us is that their continuations are never executed synchronously (even when they could), which prevents the problem
10.
by henriqueinonhe 3y ago
It's as @AgentME said, it is just meant as a disclaimer that the project should be installed via the "installer", i.e. `npm create promises-training@latest`, otherwise the project won't work as expected. But I agree the
11.
Promises Training: Practical Exercises on Promises in JavaScript(github.com)
87 points by henriqueinonhe 3y ago|63 comments
12.
by henriqueinonhe 3y ago
Recently I've created a project to help people deepen their knowledge on Promises in Javascript beyond the basics by working through a series of practical exercises, where each is accompanied by a set of automated tests.