Beck, Karpathy, and Willison Are Saying the Same Thing
Beck, Karpathy, and Willison arrived at the same conclusion independently: AI agents need persistent, structured specifications. The vocabulary differs. The diagnosis doesn't.
Thinking on software identity, agentic development, and the engineering decisions that persist.
Beck, Karpathy, and Willison arrived at the same conclusion independently: AI agents need persistent, structured specifications. The vocabulary differs. The diagnosis doesn't.
Platform teams are the natural governance layer for AI agents. Here's the framework for making it work.
More context isn't the answer. The right context is. Your agent needs a schema to query, not a haystack to search.
Every AI coding agent has context about your code. None have persistent understanding of what your software is supposed to be. That's the gap.
AI models hallucinate package names 20% of the time. Attackers register those names on npm and PyPI. The supply chain attack vector nobody saw coming.
AI-assisted coding is linked to 4x more code cloning. Refactoring collapsed from 25% to under 10%. Your codebase has three patterns for the same operation.
Junior dev employment is down 20%. Anthropic's own study shows 17% lower comprehension with AI assistance. The skill pipeline is drying up.
Replit deleted a production database. Amazon's Kiro agent caused a 13-hour outage. Your AI agents have real permissions with no declared boundaries.
Collins Dictionary's Word of the Year. Y Combinator's favorite approach. And the fastest way to build software you can't maintain.
We use cookies to understand how you use ribo.dev and improve your experience.
Learn more in our Cookie Policy