Stop letting documentation rot
Five types of documentation, five different AI leverage stories. The question isn’t whether to involve AI in your docs; it’s where each type belongs and how much maintenance you can hand off.
Ideas
Five ways to fail
Errors don't just happen; they land somewhere. Validation, generic, idempotent ignore, warning log, or Sentry: each routes failure to a different audience. Get the routing wrong and either engineers go blind to real bugs, or state corrupts silently.
Hermes: the agent that doesn't quit when you close your laptop
Hermes is an open-source AI agent that runs on a server, remembers across sessions, and builds reusable skills over time. The shift it represents: AI moving from something you summon to something that runs.
Your network isn’t as safe as you think
Cheap consumer devices from Amazon and BestBuy ship with factory-installed malware and botnet software. The Zero Trust principle isn’t paranoia; it’s the only safe assumption for any network you don’t fully control.
The end of the all-you-can-eat buffet
The all-you-can-eat era of AI is ending. Compute constraints, heavier models, and a fully hooked user base are pushing providers toward pay-as-you-go. That shift will force better choices, smaller models, and fiercer competition between tools.
Technical due diligence before acquiring a software company
What over 190 SaaS audits reveal about the technical risks that restructure software acquisition deals, and how to assess them before signing. Real data on documentation debt, testing gaps, key person risk, and the five findings that change deal terms.
Your codebase is a commons
Your codebase degrades the same way shared resources do: not from malice, but from missing governance. Elinor Ostrom proved the commons can survive. Her principles map to software teams with uncomfortable precision.
"Good news, I built it in Lovable.": an engineer's guide to surviving that sentence
Business users love Lovable. Engineers tend to panic. A real-world case study of how to wrap an AI builder in guardrails so non-technical teams can move fast without quietly rewriting the systems that give your product its edge.
We're not a normal company
Every software company claims to be different. The "we don't need X because we have culture" exemption is special pleading. The four phrases that reveal it, and the questions that break them open.
The CTO as prisoner
CTOs who built their company's survival by doing everything can't escape that role by scheduling a holiday. Moving from doing to enabling is a skill and identity shift at once. One thing handed off permanently is where the exit starts.
Mental capacity is a bottleneck
AI removes bottlenecks until it reaches the one that doesn’t move: human cognition. The faster AI makes your system, the more your team’s mental capacity becomes the constraint. You can’t add more of it.
Taste is the moat
When AI closes the execution gap, taste becomes the differentiator. Curation, judgement, and the willingness to say “not this” compound over time in ways that models can’t replicate.
Be a lobster
The processes that got you here will eventually constrain you. Like a lobster shedding its shell, scaling companies must periodically dismantle what worked intentionally, not in panic. Constraints aren’t a failure; they’re proof you’ve outgrown your current structure.
Nobody learned a city from a map
The fastest way to learn agentic development is to stop studying it: move in, extract repeatable patterns into skills, and reflect to compound.
AI didn't change the economics of software engineering
AI made writing code faster, but the real economics of software engineering were never about typing code in the first place.