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 →A live, clickable presentation - built in Claude Design itself - walking through what the tool is, where it fits a designer's week, and the real sites shipped with it.
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 →Design systems, UX and UI fundamentals, and the tools design work ships through - plus how design hands off to engineering.
Open this path →Distributed systems, instrumentation, and the platform craft beneath every product.
Open this path →Launch it, write the content, run the ads, read the SEO, wire the analytics - the growth stack modern builders ship alongside the product.
Open this path →Modern build tooling and the frameworks shaping the next decade of the browser.
Open this path →Curated reading orders across the library - each one sorts a subject into layers and tells you where to start. Maps can pull articles from more than one Path, which is the point of having them. All maps →
The agent slice of the AI library, walked in full - the idea, the context window, the extensions, the architectures past one agent, and what production takes - with three reading orders.
Open the map →The narrower cut of the AI library - just the tools that show up in a developer's day-to-day. Coding with Copilot or Claude Code, delegating to Claude Cowork, designing with Claude, generating images, plus the model and protocol underneath.
Open the map →Every AI Path article sorted by layer - from foundation models up to the developer tools - with three reading orders for developers new to AI, agent builders, and depth-first readers.
Open the map →The adoption route for a designer meeting Claude Design - the tool, the design-system language it reads, making yours machine-readable, and the fidelity ladder it hands back.
Open the map →Every Design Path article sorted across eight layers - language and tokens, craft, vocabulary, fidelity, tools, handoff, brand and graphics - plus the AI design layer on top, with three reading orders.
Open the map →The platform craft underneath modern software - orchestration with Aspire, observability across services, and API documentation on top of OpenAPI. Three layers, every Engineering Path article in scope.
Open the map →The flagship route across every Path - design, build, ship, and grow a product end to end, with AI woven through, plus three reading orders for founders, developers, and managers.
Open the map →Every Web Path article sorted by layer - language, build tools, frameworks, API docs, orchestration - with a one-line reason and three reading orders for different readers. Pulls in API doc pieces from Engineering.
Open the map →