Vibe Coding

Ever notice how in sci-fi films, everyone seems to know how to work with technology? There are no "non-technical" beings because most are born digitally native. They just speak to AI systems to get things done. That's where we're heading with what Andrej Karpathy calls "vibe coding" - using AI to build software while focusing on the experience rather than the technical details.

I've noticed this elitist response from traditional developers. They're salty about the flood of new builders who don't do things "the right way". But here's the thing about platform and audience shifts - I'd rather lean into the group who sees what's possible (they'll be the innovators) than those stuck in the old ways. When surfing, you lean into the wave. Same with tech - experimentation plus experience equals novelty. And right now, we're seeing a massive wave with AI-IDEs and generative platforms exploding the software market wide open.

When I'm vibe coding, I actually focus more on the vibe than the code. Sometimes I make super simple mistakes because I'm lost in crafting an experience. And that's okay. I'm trying to connect my empathy to user problems without getting caught up in code architecture. Focus on solving real user problems first. Let AI handle the technical heavy lifting. Build for the experience, not technical perfection. Trust that future AI will help refactor and improve the code. Make building feel like play, not work.

Here's what's interesting - a lot of traditional developers actually lack empathy because they're so focused on code and reliant on a PM. Bless them for making Gen-AI possible, but there's room for a different kind of builder. Now I can focus on creating memorable product experiences, designing delightful interactions, understanding and solving user problems, and building with empathy first, code second.

I want software to feel more like a game. Imagine work feels like a quest, tools feel like your inventory, results feel like finishing a boss fight, commanding AI agents like an RTS game, collaborating with co-workers like guild mates. Is it too much to ask? Maybe. But that's the kind of future I want for software. We're moving from developers being craftspeople who painstakingly write every line of code, to directors who orchestrate AI agents to bring their vision to life.

At the end of the day, building quality software is about providing enough value to users that it outweighs the cost or time of doing it themselves. By removing technical friction, vibe coding lets us focus on what really matters - understanding and solving user needs throughout the development process. Don't worry too much about perfect code right now. Future AI will help clean things up. Is this an excuse for sloppy code? No, but it buys us time to focus on what matters most - creating software that people actually want to use.

Want to dive deeper? Check out these posts:
- [Building Full Stack Apps with AI](/posts/one-shot-apps)
- [The Future of AI IDEs](/posts/ai-ides)
- [Deep Research List](/posts/deep-research-list)