AI is collapsing the traditional role hierarchy in software. Vibe coding absorbs product management; model training absorbs traditional coding. ## Core Insight > "Vibe coding is the new product management. > > Training and tuning models is the new coding." > — Naval Ravikant ## Key Principles 1. **Role compression**: AI doesn't eliminate roles — it redefines which activity maps to which traditional role 2. **Vibe coding as PM**: When anyone can translate intent into working software through natural language, the bottleneck shifts from "can we build it?" to "what should we build?" — historically the PM's job 3. **Training as coding**: The new "implementation" is shaping model behavior through training data, fine-tuning, and prompt engineering — not writing explicit logic 4. **Upward shift**: Each role in the stack absorbs the one below it. Coders become model trainers. PMs become vibe coders. Strategy becomes the new PM ## Implications - **For experienced developers**: Domain knowledge and system design judgment become the differentiator, not syntax fluency - **For product managers**: Their role doesn't disappear — it transforms into the person who can directly prototype through vibe coding - **For career planning**: Invest in the layer above your current role, not deeper into the one being absorbed ## Connections - [[Experience as AI Multiplier]] — Experience in system design is what makes vibe coding produce good results - [[Leverage Erosion Trap]] — The value of traditional implementation skills erodes before the job title changes - [[Register Keyword Analogy]] — Uncle Bob's parallel: we're at the same abstraction transition point as C's register keyword ## Source - [[Recent Highlights Feb 4-7 2026 - Highlights]] — Naval tweet, highlighted 2026-02-04 - [Readwise](https://readwise.io/open/984736271)