TL;DR: Four posts this week, and three of them circle the same uncomfortable idea: a system rarely sees its own blind spot. A content pipeline that approved a claim its own source contradicted, a qua…
2026
TL;DR: Three posts this week. Two are about the stuff an agent reads; one is about what an agent is measured on. The first is a small Bedrock experiment showing that a “sponsored” block in agent-read…
TL;DR: Three posts this week, and they rhyme: each one looks past the loud, obvious layer to a quieter one underneath. Amara’s Law says the AGI peak is what we overrate and the boring, already-useful …
TL;DR: Five posts this week, one habit worth keeping: read past the headline before you decide. A metric is not the goal it stands in for (Goodhart’s Law). A model being big is about trainability, no…
TL;DR: Three posts this week, one quiet throughline: the disciplined, bounded move keeps beating the maximalist one. Gall’s Law says you compose a complex system from small working bricks instead of …
TL;DR: Three posts about where the human stays in charge as agents do more of the work. “Laws & Disorder” closes with Tesler’s Law: you can’t delete a system’s complexity, only choose who owns each pi…
TL;DR: Three posts about the cost you can’t see until you go looking. “Laws & Disorder” continues with Hyrum’s Law: every observable behavior of your API is a contract someone depends on, and AI agent…
TL;DR: Three posts, one quiet theme: the structure you don’t design still gets drawn. “Laws & Disorder” opens with Conway’s Law — your architecture mirrors your org chart, so shape the teams first, an…
TL;DR: This week was about taking a big idea off the whiteboard and finding the exact AWS building block that turns it on. Two posts continue the “Whiteboard to Cloud” series: compression as the clean…
TL;DR: This week was about where knowledge lives, who owns it, and where the real work actually is. Three posts climb the agent-memory ladder: naming the spectrum, then the retrieval mechanism (vector…