Blog
Notes on AI, properly done.Copy link
Weekly essays on methodology, agents, products, and what breaks when AI meets real software. Written as the work is done.
-
Start here
AI software, properly. Copy link
Some context. Where this site is coming from, and why I've stopped pretending the way most companies build software is normal.
-
Context engineering. The model isn't wrong. It's weighting the wrong thing. Copy link
The craft moved upstream, to requirements and architecture. Context engineering is the orchestration tier inside that.
-
Vibe coding belongs upstream of the PRD. Copy link
Prototyping is a discovery move. Treat it as a delivery move and the audit trail starts at the moment an agent guessed.
-
The fate of the human engineer. Copy link
The role was never static. AI just made the rate of change impossible to ignore.
-
Ninety-six percent don't trust AI code. Half of them check it. Copy link
The AI trust gap is a methodology problem, and the industry keeps reaching for tooling instead.
-
How much do you trust human output? Copy link
Every AI failure mode has a human equivalent that predates large language models by decades. The common root cause is the one nobody wants to examine.
-
Nobody owns the requirements anymore. Copy link
Requirements used to be somebody's job. Then we hollowed the role out, and now AI is filling the gap with guesswork.
-
The last twenty percent. Copy link
What's actually hiding in the part of the build that AI skips past, and why it still bites.