The Next Decade Looks More Like Terraform Than GitHub
Terraform proved infrastructure should be declared. The same transformation is coming to application software. The specification becomes the source of truth.
Thinking on software identity, agentic development, and the engineering decisions that persist.
Terraform proved infrastructure should be declared. The same transformation is coming to application software. The specification becomes the source of truth.
Everyone's talking about AI code quality. The actual problem is cognitive debt, verification debt, and architectural debt, and your linter can't catch any of them.
The first wave of vibe-coded startups is hitting a wall. The survivors won't be the ones who abandoned AI. They'll be the ones who defined what their software is before they let AI build it.
EU AI Act enforcement hits August 2026. Colorado's AI Act hits June 2026. Most engineering orgs have zero governance for AI-generated code. The audit is coming.
AI is making rewrites cheap. But 70% still fail. The code is disposable. The contracts are not.
Bill Eisenhauer proposed that specifications are the durable artifact and code is a regenerable rendering. The natural next question: what does the infrastructure look like that makes that work at enterprise scale?
Every compliance tool tells you you're broken. None of them fix it. What if a single declaration triggered automatic, codebase-wide reconciliation?
If you were hiring today knowing AI writes 41% of the code, would you build the same org? The roles, the teams, the governance -- it all changes.
Your auditor will ask who wrote the code, against what specification, and how you verified it. Here's how to have answers.
You wrote a spec. Your AI agent ignored it. Here is why, and how to write specifications that agents actually respect.
We use cookies to understand how you use ribo.dev and improve your experience.
Learn more in our Cookie Policy