Writing
Notes from the last mile.
Articles on AI governance, spec-driven development, and building systems that compound.
The Enso series
Six pieces on why AI-assisted work needs a discipline, and what that discipline is. The methodology itself is on the Enso page.
- AI Coding Assistants Are Powerful. They’re Also Ungoverned.The problem isn’t the tools. It’s the absence of a methodology.
- No Spec, No WorkDocumentation isn’t the artifact. It’s the blueprint.
- Your AI Is Writing Code for AttackersOffense has automated. Defense is still playing catch-up.
- Why Better AI Won’t Save YouSmarter models don’t solve the governance problem. They make it worse.
- Validation Is a Loop, Not a GatePoint-in-time checks don’t catch drift. Continuous validation does.
- Beyond CodeSpec-driven methodology isn’t just for software. It’s for any domain where outputs must match intent.
Other writing
- I Tracked Extremists for Years. Now I See Their Playbook Everywhere.What years in threat intelligence taught me about pattern recognition, and why I see the same tactics everywhere now.
- Is AI Really Draining Water? The Story You Haven’t Heard.Cutting through viral narratives with actual infrastructure expertise.
Let’s talk.
If you’re putting AI into production in healthcare, or anywhere a deployment that almost works isn’t good enough, I’d like to hear about it. A 15-minute call is a good start.
Book a call