Tag
Architecture
9 essays
Filed under9 filed
What I Learned Building a Document Format from Scratch
I started thinking the hard problem was document parsing. Then format design. Then sync logic. The real challenge was building at the interface between two domains that don't talk to each other.
The Design Decisions Behind an AI-Native Document Format
Processing a Word document through raw OOXML costs 359,706 prompt tokens. Clean markdown costs 106. Five design decisions that make that gap useful without losing formatting.
Why AI Document Workflows Are Broken
Every AI tool that works with documents treats formatting as disposable. For organizations running hundreds of documents through AI editing pipelines, it's a structural cost nobody is tracking.
Goal Translation Infrastructure: Encoding What Your Organization Actually Wants
Your Capability Map says a workflow is Agent Ready. Now what does the agent optimize for? OKRs were designed for humans. Agent Actionable Objectives are the translation layer that's been missing.
The Organizational Capability Map: Deciding What Your AI Agents Should Actually Own
Most AI deployments fail not because the technology doesn't work, but because nobody decided which workflows agents should actually own. The Organizational Capability Map is a framework for making that call.
The Intent Gap: Why Your AI Agents Are Optimizing for the Wrong Thing
Klarna's AI agent saved $60M then backfired. The problem wasn't the AI. It was the gap between what agents optimize for and what organizations actually need.
Stop Waiting for Legacy Systems: How the Strangler Pattern Fixes Real Integration Problems
A manufacturer's web store took 12 seconds per order because of synchronous SAP calls. Customers abandoned carts. We fixed this with the strangler pattern - not by making SAP faster, but by stopping the wait for SAP. Real code examples included.
Moving from Engineer to Architect: The Skills That Matter
The shift from engineer to architect isn't about learning new tools. It's expanding your scope from local fixes to global impact. Engineers make code work. Architects think about what happens when that code scales, fails, or succeeds beyond expectations.
When Kubernetes Isn't the Answer: Right-Sizing Your Cloud Architecture
Teams pick Kubernetes before they understand their problem. This creates unnecessary complexity. I've seen simple apps that would work perfectly on Azure App Service struggle with container orchestration nightmares. Requirements should drive platform choice, not trends.