Naval's Playbook, Re-read in the Age of AI
“Learn to sell. Learn to build. If you can do both, you will be unstoppable.” — Naval Ravikant
I’ve been re-reading Naval’s ideas — the almanack, the tweetstorms, the podcasts. What strikes me is how much more relevant they become when AI rewrites the rules of leverage.
The Ideas That Hit Different Now
1. Specific Knowledge
Naval says: “Specific knowledge is found by pursuing your genuine curiosity, not by following whatever is hot.”
In 2026, “hot” is prompting, fine-tuning, and AI wrappers. Everyone is chasing the same tutorials. But specific knowledge is the thing AI can’t easily replicate about you — your unique intersection of domain expertise, taste, and judgment built through years of real problems.
As a software engineer: your specific knowledge isn’t “I can write code” — AI does that now. It’s “I know why this system failed at 3am, what trade-offs led there, and how to design so it doesn’t happen again.” Systems thinking, operational intuition, architectural judgment — these compound in ways that don’t get commoditized overnight.
2. Leverage Has a New Form
Naval’s three leverages: labor, capital, and products with no marginal cost of replication (code and media).
AI just 10x’d the third one. A single engineer with AI can now ship what used to take a team. A single writer with AI can produce at the volume of a small publication. The leverage is asymmetric in favor of people who already know what to build and why.
But here’s the catch: if everyone has the same AI leverage, the differentiator goes back upstream — to judgment, taste, and knowing which problem is worth solving.
3. “Earn with Your Mind, Not Your Time”
This was always true for senior engineers. But AI makes it urgent for everyone.
If your value is “I write 200 lines of code per day,” you’re competing against a machine that writes 2000. If your value is “I know which 20 lines actually matter and why,” you’re irreplaceable.
The shift isn’t about learning to prompt. It’s about moving up the abstraction ladder — from execution to decision-making, from implementation to design, from coding to thinking.
4. Compounding and Long-term Games
Naval says: “Play long-term games with long-term people. All returns in life come from compound interest.”
In AI’s hype cycle, everyone is playing short-term games — chasing the next model drop, the next framework, the next viral demo. But compounding still works the same way:
- Deep expertise in one domain compounds.
- Trust with collaborators compounds.
- Writing and thinking in public compounds.
- Understanding fundamentals compounds.
The engineer who spends three years deeply understanding distributed systems will outperform the one who spent three years chasing every new AI tool — because foundations compound, tools deprecate.
5. Judgment Over Hours
“Judgment — especially demonstrated judgment, with high accountability and a clear track record — is critical.”
AI compresses execution time. A task that took two days takes two hours. This means the bottleneck shifts entirely to judgment:
- What should we build?
- What should we NOT build?
- Which risks are acceptable?
- When is “good enough” actually good enough?
The engineers who rise now are the ones who make the right calls, not the ones who type the fastest.
My Takeaway
Naval’s framework was always about escaping competition through authenticity — be so specific in your combination of skills that no one can replace you.
AI didn’t break this framework. It accelerated it.
The engineers who treat AI as “a thing that replaces my coding” will feel threatened. The engineers who treat AI as “leverage that amplifies my judgment” will build things that were previously impossible for a single person.
The question isn’t “will AI take my job?” It’s Naval’s original question reframed: “What can I build that’s so specific to my curiosity, my judgment, and my taste — that even an AI with infinite execution capacity wouldn’t know to build it?”
That’s the game now. Same rules. Higher stakes. More leverage for those who play it right.