Every working stack is the residue of failures the operator did not see coming. The Saturday piece showed the architecture as it stands now. This piece is the inverse — the five specific incidents that produced the current shape. Each one started as a quiet bug and ended as a permanent

Most "AI is expensive" discourse is vague. The pieces that quote real numbers usually quote enterprise tier list prices for tools the writer does not personally run. The pieces that talk about personal use rarely quote any numbers at all. This is the ledger for a working personal

The dotfiles piece from May 22 named hooks as one component of a personal AI stack and moved on. They deserve more than a passing mention. Hooks are the primitive that turns taste into code — the editor's auto-format-on-save for AI work, run on the agent's actions

Yesterday's piece prescribed building a personal AI stack instead of waiting for the enterprise plan. The natural objection — "fine, but what does that actually look like" — deserves a concrete answer. So here is mine, opened up. This stack ships a five-surface content pipeline daily, on cron,

Every senior engineer who has shipped meaningful work in the last thirty years has carried a personal dev environment with them. Emacs configs, vim plugins, shell aliases, dotfiles repos, custom prompts, terminal multiplexer setups, a handful of scripts that exist only on their laptop and do exactly what the work

The current "Hermes Agent vs Claude Code" framing is the wrong comparison. The two tools live at different layers of the coding agent stack, and most of the YouTube hot takes treating them as alternatives are reading them as if they competed for the same job. They do

An article circulating this week argues that faculty AI buy-in in higher education is a human factors engineering problem. The framing is correct. The path the piece describes skips the only two steps that matter, and the reason it skips them is structural, not pedagogical. Start with the framework on

Anthropic added the /goal command to Claude Code in v2.1.139. You set a completion condition; the agent keeps working across turns; a second model reads the transcript and decides whether the condition was met. It is the built-in version of the keep-going loops people have been hand-rolling for

A DevOps engineer posted on r/devops this week with what reads like a familiar shadow-IT question dressed in 2026 clothes. Marketing, product, and sales people across his AI startup are shipping internal apps with Cursor and Claude Code. They deploy to Vercel, Cloudflare Pages, Netlify. The data is real.