Points of view on enterprise architecture, AI adoption, and technology leadership in regulated organisations.
I built an AI assistant over structured enterprise data. The inconsistent answers weren't a model failure — they were a semantic debt problem the AI made impossible to ignore.
Strong opinions, loosely held. Here's what that actually means.
Since Mythos dropped, the security community has had plenty to say. What nobody is talking about is what it means for your engineering investment.
The static architecture document isn't just out of date. It's the wrong object entirely. And the architects who survive this moment will be the ones who figured that out by shipping something real.
Your AI coding agent doesn't know your architecture standards. It doesn't know your ADRs, your principles, your data classification rules. And it's making decisions on your codebase every day without them.
We rebuilt the ailíniú website using AI as a collaborator, not a shortcut. The words took longer than the code, and the skills that make enterprise architecture effective turned out to be exactly what made AI-assisted development work.
Most people use AI coding tools the same way. Open a session. Explain the project. Build something. Close the session. Next session. Explain the project again. The problem isn't the tool. It's the onboarding.
A former colleague's comment stopped me in my tracks. On operational experience, hard-won instincts, and what a nine-phase process can and can't encode.
Boris Cherny said a coder is now more like an architect than a construction worker. I read that from the other side of the transition — an enterprise architect who discovered he could actually build.
On retrieval augmented generation, multi-agent swarms, and why context engineering is the discipline the EA community is uniquely positioned to lead.
The fix wasn't a better AI. It was a better briefing. How a nine-phase process and seven documents changed the way I build with AI.
Everything that made AI-assisted development work well turned out to be just good architecture practice. The skills I'd spent years building weren't a disadvantage. They were a significant advantage.
