Writing on React, web performance, and the craft of building software.
Why this series solves the same async problem seven different ways instead of teaching one correct pattern.
Why JavaScript running on a single thread means nothing here ever truly happens in parallel, no matter how concurrent it looks.
What callback hell actually is underneath the nested indentation, and the two deficiencies that make it worth solving at all.
A function that already carries everything it needs to produce a value later, and why that turns out to be a preview of promises.
The API, the trust guarantees a callback never gave you, and chaining them into real sequential flow control.