Adding to DNA Is a Decision. Adding to Code Is Just Typing.
When AI makes execution cheap, the scarce resource is not typing. It is deciding. The discipline of the next era is knowing the difference.
Thinking on software identity, agentic development, and the engineering decisions that persist.
When AI makes execution cheap, the scarce resource is not typing. It is deciding. The discipline of the next era is knowing the difference.
Beck, Karpathy, and Willison arrived at the same conclusion independently: AI agents need persistent, structured specifications. The vocabulary differs. The diagnosis doesn't.
Context changes per request. Identity persists across sessions, tools, and team members. Context engineering without identity engineering is a database query without a schema.
Your AI agents have credentials, make API calls, and access production data. They're operating on borrowed human identities with no scoped permissions. That's an identity crisis.
Twitter rewrote Ruby to Scala. Uber's microservices have a 1.5-year half-life. The code is always temporary. The question is what persists.
The $6 billion documentation industry is solving the wrong problem. You don't need better docs. You need software that knows what it is.
Spec-driven development is a paradigm where specifications are the primary artifact and AI agents generate code from them. Here's how it works, who's doing it, and where it's heading.
Software DNA is a declarative identity layer that defines what software is, what it should do, and what constraints it must honor. It's the primitive the industry has been building around without building.
Software runs the financial system, the power grid, the hospital. It has no persistent identity. In an era where 41% of code is AI-generated, that's existential.
We use cookies to understand how you use ribo.dev and improve your experience.
Learn more in our Cookie Policy