Software Survival 3.0
Summary
Yegge proposes a framework for predicting which software will survive in Karpathy's 'Software 3.0' era where AI writes all code. He argues that resource constraints (tokens, energy, money) create selection pressure favoring software that saves cognition. He presents a 'Survival Ratio' with six levers: insight compression (crystallized knowledge like Git), substrate efficiency (CPU beats GPU for tasks like grep), broad utility, publicity/awareness, minimizing friction for agents, and a human coefficient for human-preferred software. He concludes optimistically that demand for software is infinite and builders have multiple paths forward.
Key Insight
In a world of AI-written software, the selection pressure of constrained compute resources will favor tools that save more cognition than they cost to discover and use — crystallized knowledge and substrate-efficient computation become the ultimate survival advantages.
Spicy Quotes (click to share)
- 6
All of my predictive power comes from believing the curves. It's that simple.
- 5
Software tends to survive if it saves cognition.
- 6
An AI reimplementing Git from first principles would have to re-traverse that entire intellectual history, burning tokens all the way. It would be economically irrational.
- 7
Nobody is coming for grep.
- 5
Our ambition will always outstrip available cognition. Token costs will fall, but we'll keep moving the frontier, generating more work than there are tokens to perform it.
- 8
If even North Korean hackers understand Agent UX, then it's probably time you did too.
- 4
Build something that would be crazy to re-synthesize. Make it easy to find. Make it easy to use. Then I think you've got a solid shot.
Tone
opinionated, conversational, optimistic
