AI
Build with the new generation of agents. From prompting fundamentals to design systems for AI surfaces.
Open this path →Four articles we keep coming back to - one story about what Claude Code actually changes, one focused essay on Copilot vs Claude Code, the short read on the toolchain every web developer should know in 2026, and the runtime-internals deep dive on the JavaScript event loop.
A real 2018 snake game - ASP.NET Core, gulp, .cshtml, scattered JavaScript - migrated to HTML5 + TypeScript + esbuild in a single Claude Code session. Twenty minutes of work, screenshot by screenshot.
Read the article →
A focused take on the one axis that most decides which AI pair programmer fits which task. One tool ships clean parts; the other proposes whole designs. Knowing which is which is most of the choice.
Read the article →Four tools shape how a modern frontend gets built and shipped: esbuild, Vite, TypeScript, and the JavaScript flavor of Aspire. What each one does, how they fit together, and what you can skip.
Read the article →
How a single-threaded language handles concurrency without blocking. The call stack, the host environment, the task and microtask queues, and the algorithm that ties them together - paired with Philip Roberts' definitive JSConf talk.
Read the article →Four Maps that tie our growing library together - the modern web stack, the broad AI stack, an AI subset for developers, and the engineering platform underneath. Each sorted by layer with reading orders for different kinds of reader.
The narrower cut - just the AI tools that show up in a developer's day-to-day. Coding with Copilot or Claude Code, designing with Claude, generating images, plus the model and protocol underneath.
Every AI Path article sorted by layer - from foundation models up to the daily tools - with three reading orders for developers new to AI, builders shipping agents, and depth-first readers.
The platform craft underneath modern software - what your services run on, how you find out what they are doing, and how you document the contract between them. Three layers, every Engineering Path article in scope.
Every Web Path article (plus the Engineering API doc pieces) sorted by what they cover, with three reading orders for returning developers, backend devs wiring up a frontend, and depth-first readers.
Every path is a curated sequence - built to take you from first principles to shipping in production, without the detours.
Build with the new generation of agents. From prompting fundamentals to design systems for AI surfaces.
Open this path →Containers, orchestration, and the runtime your services actually run on.
Open this path →Schemas, queries, and the storage decisions that outlast every framework. The data layer, without the hand-waving.
Open this path →From wireframe to handoff - design systems and the daily tools that make them real.
Open this path →Distributed systems, instrumentation, and the platform craft beneath every product.
Open this path →Modern build tooling and the frameworks shaping the next decade of the browser.
Open this path →