Tools he uses: Lovable, Cursor, Claude Code, ChatGPT
The workflow: describe → generate → test → iterate → deploy
Bugs are fixed by prompting, not debugging in the traditional sense
The learning curve: taste and specification > syntax and algorithms
What he optimizes for"I'm optimizing 100% of my time today on good judgment, clarity, quality, taste."
What Vibe Coders Build
Real Products, No Traditional Coding
Internal tools: Admin dashboards, data pipelines, workflow automation
Customer-facing: Shopify integration templates and the Lovable merch store
Prototypes: 30-minute demos handed off to engineers to replicate in production
Where elite engineering is still needed: maintaining and scaling code bases, and infrastructure
The quality ceiling
Vibe coding hits walls at system design, scalability, and security. Know where to hand off.
The new PM
Vibe coders are collapsing the PM + engineer + designer into one role for certain products.
Playbook
Become a Vibe Coder
Master specification: the clearer your vision, the better the output
Learn to evaluate code quality without reading every line, use tests, user behavior, error logs
Build in public: share what you built, get feedback, iterate fast
Toolkit he names: Lovable, Cursor, Claude Code, ChatGPT (custom GPTs for PRDs)
Where this is going"Vibe coding is just coding in 12 months from now."
Contrarian
What Vibe Coding Challenges
✗You need CS fundamentals to build softwareINSTEAD →✓ You need product fundamentals. Understanding users matters more than understanding pointers.
✗Tell a young person to get a CS degreeINSTEAD →✓ "If I had an 18-year-old brother and he asked me what should I do, I would tell him, 'Go become a plumber. Don't go and get a CS degree. Learn a good trade.'"
✗This is just a toyINSTEAD →✓ At least half of S&P 500 companies have people using Lovable. Vibe-coded tools are in production at real companies today.
✗Real engineers don't use thisINSTEAD →✓ Real engineers use AI tools. "Vibe coder" is just the name for people who go all in.