Home

This post reframes system architecture not as a technical challenge, but as a social one. It argues that the most resilient and scalable systems aren’t built on code, but on well-designed agreements between teams. By treating contracts, APIs, and documentation as promises, we can shift our focus from implementation to intent, creating systems that scale organizationally because they’re built on a foundation of human trust.

In response to the panic that agentic AI shortens the path to expertise, this post reframes the ten-year journey to mastery. The time required remains non-negotiable, but its focus shifts from writing code to conducting AI. The new path to expertise is defined by the deliberate practice of prompt engineering, critically evaluating AI output, and applying the deep judgment that can only be built over a decade of experience.

When faced with an ambiguous problem, the instinct is often to plan and research our way to a perfect solution. This is a trap. Clarity isn’t found in a document; it’s earned through action. The most effective strategy for navigating uncertainty is to take the smallest possible step, write the “bad” code, and create a feedback loop. Momentum is a strategy. Moving your feet is the only way to find the right path.

Before sailing further, we stop and take stock. This post is a honest reckoning with what Part 1 built—a semantic, accessible, typographically intentional, offline-capable reader—and what it still can’t do: persist settings across reloads, manage more than one zine, link between issues, or scale its markup without growing unwieldy. The checkmarks are real, but so are the failures, and the failures are the fuel for Part 2.

If you can’t read it offline, you don’t truly possess it. This post crosses the first real threshold of the series—introducing JavaScript not as interface logic but as infrastructure—by implementing a Service Worker that intercepts network requests and serves the entire reader from a local cache, making the application functional with no connection at all.

We are guests in the user’s browser—we don’t repaint their walls without asking. This post gives the reader direct control over their experience, building a CSS-only settings system: a sliding drawer, a theme toggle, adjustable text size and line height, with no JavaScript and no runtime cost. The Siren’s Call whispers to reach for an event listener; instead, we learn the grammar of the platform.