The closing batch, about craft, strategy, and the new shapes engineering roles are taking.
Brad Frost’s I Redesigned My Website Without Touching My Keyboard is exactly what it sounds like. He directed Claude Code entirely by voice while physically painting a mural in another room. The redesign wasn’t trivial, it involved layout changes, component updates, and style revisions. His takeaway isn’t “look how easy this is” but rather an observation about what voice interaction does to the collaboration dynamic. Speaking instructions forces you to think at a higher level of abstraction. You can’t micromanage individual CSS properties when you’re dictating from across a room. The result is a different kind of creative direction, one that focuses on intent rather than implementation.
Justin Butlion’s My 5th SaaS Acquisition is a transparent portfolio update from someone who buys small SaaS products rather than building from scratch. He walks through the economics of each acquisition, the MRR trajectories, what he changed post-acquisition, and what he left alone. The strategy is clear: buy products with existing revenue and customers, apply operational improvements, and compound. It’s a useful counterpoint to the “build from zero” startup narrative and a good data point for anyone considering the acquisition path.
Steve King’s How to Lead Remote Engineering Teams is a practical guide from someone who’s done it across multiple companies. The advice is specific: default to async, make decisions visible in writing, schedule synchronous time only when it’s genuinely needed, invest in onboarding documentation, and be explicit about response time expectations. The section on “presence inequality”, where team members in the same timezone as the lead get disproportionate access, is the kind of thing that’s easy to miss and hard to fix once it’s embedded in the culture.
Steve Yegge’s Vibe Maintainer is a characteristically provocative Yegge essay about the new archetype for senior engineering in an AI-assisted world. His argument: the most valuable person on a team is no longer the fastest coder but the person who maintains the “vibe” of the codebase, the coherent set of patterns, decisions, architectural intentions, and naming conventions that make the whole thing feel like one project rather than a patchwork of agent-generated fragments. The vibe maintainer reviews, refactors, sets direction, and keeps the codebase legible. It’s a reframing of technical leadership that I found genuinely clarifying.
Gas Town and Bullet Hell is a cultural essay that uses gaming metaphors to talk about navigating the AI era. The writing is sharp and the framing is unusual, it treats the current moment not as a transition to be managed but as a new kind of environment to be played skillfully. I found it refreshing precisely because it doesn’t try to resolve the tension between optimism and anxiety; it treats both as reasonable responses to an unreasonable pace of change.