Writing

A memory feature that prunes itself while you sleep is exactly what long-running agents need. The version that briefly shipped in Claude Code can also delete files without telling you, and silently stop running when it crashes. I want it back, with better manners.

The people shipping with agents in 2026 aren't the ones who can spell MCP. They're the ones who can read a five-year-old codebase in an afternoon and tell you which migration is keeping the team awake.

An honest log of one Saturday on Jobado: when I drove, when I steered, when I had three agent sessions running at once. Including the two times I had to undo the agent's work, and why I think that's still a win.

AI accelerates the typing. It does not accelerate the judgment. Most senior work isn't building. It's the careful undoing of last year's correct decisions.

Two versions of seniority. Both real. One is undervalued in 2026 hiring, and I want to make a small case for it.

Wedding-planning SaaS has a strange constraint: most failure modes are tolerable Monday morning. The one on the wedding day is not. Building for that asymmetry changed how I think about availability.

The most senior engineer in a room is usually the calmest. They've been wrong enough times to know the cost of dramatic certainty.

Most of the value I get from MCP isn't novel agent capability. It's the same connect-and-call ergonomics every codebase has wanted from its IDE for fifteen years.

A pragmatic, ordered checklist. Where the trust lives, where the load-bearing decisions hide, and the three files that almost always tell you the truth about a team.

An end-of-year list. Not what's new, but what I've quietly stopped saying. Including 'we'll fix it later,' 'just one more abstraction,' and 'they'll read the README.'