3 ms·
I get why some people are skeptical of “vibe coding”—it sounds like AI blindly generating code and hoping it works. But that’s not really what’s happening. It’
by jonthebeef 2y ago
I get why some people are skeptical of “vibe coding”—it sounds like AI blindly generating code and hoping it works. But that’s not really what’s happening.
It’s not about replacing solid engineering principles or craftsmanship—it’s about shifting how we interact with code. Instead of micromanaging every function from the start, you set intent and iterate quickly. It’s more like pair programming with an AI that can help you move faster, not handing over control entirely.
I wrote about this after using DeepSeek R1 + Cursor to prototype an AI chat interface for my Raspberry Pi NAS. It still took over 100 prompts to refine, but it turned what was in my head into something real and functional—faster than if I’d started from scratch. The key is treating AI as a collaborator, not a crutch.
If you’re interested in how natural language + agentic interfaces change how we build, I wrote more on it here: https://productandrobots.substack.com/p/its-a-vibe-dude https://productandrobots.substack.com/p/its-a-vibe-dude.
Curious—has anyone else tried pushing AI beyond just simple code generation? How do you think this approach plays out long-term?