Start Learning From the Docs. Then Find Your Own Way.
Why official technology docs should be your first step when learning, how to choose videos, books, podcasts or courses next, and how to keep up with changes.

Practical, diagram-first explanations you can read over coffee. 61 posts, 122 reads and counting.

How to give feedback and run review meetings with a team member using technical evidence (PRs, CI runs, incidents) instead of opinions and drama.
Why official technology docs should be your first step when learning, how to choose videos, books, podcasts or courses next, and how to keep up with changes.

AI coding tools are assistants, not owners. Why every product needs a senior engineer to review, observe and maintain what AI builds.

How V8's generational garbage collector really charges you: scavenges cost per survivor, and allocation site pretenuring can make long-lived objects cheaper.

How memory locality and CPU cache misses affect JavaScript: why array order changes loop speed for large arrays of objects, and when typed arrays help.

Why slice() in V8 can keep a huge parent string alive, how sliced strings cause memory leaks in Node.js, and how to copy a string to release it.

How V8 hidden classes and inline caches work, why property reads jump in cost past four object shapes, and how to keep hot code monomorphic.

What layout thrashing and forced reflow are, why reading offsetWidth after a style change is so slow, and how batching reads and writes fixes it.

Why 0.1 + 0.2 !== 0.3 in JavaScript, how floating-point math drops a cent when converting dollars to cents, and why money should be stored as integers.

Short posts on one theme, meant to be read in order. Each part stands alone, and together they build the full picture.
Get new posts in your inbox
One email when a new post is out: short, diagram-first explanations of JavaScript, React and Next.js. No spam, unsubscribe any time.