There's a tension in modern software development that doesn't get talked about enough: the rise of vibe-coding in an era that supposedly values software craftsmanship.

What is vibe-coding?

Development driven by momentum and intuition rather than deep technical understanding. Copy from Stack Overflow, prompt an LLM, string together frameworks you half-understand, and ship something that works. No formal design. No real architecture. Just vibes.

And honestly? Sometimes it works incredibly well.

The craft perspective pushes back

Software craftsmanship emphasizes fundamentals — clean code, test-driven development, design patterns, intentional architecture. It's about building systems you can maintain and reason about. Code as a long-term investment, not a quick hack.

But here's where it gets interesting

Pure craftsmanship can be a trap. You can spend weeks architecting the perfect solution for a problem your users don't care about. You can refactor yourself into irrelevance while competitors ship.

Vibe-coding gets things in front of users. It validates ideas. It generates revenue.

The hybrid approach

The best teams know when to vibe-code and when to craft.

• Vibe-code: Product exploration, prototypes, throwaway experiments
• Apply craft: Core infrastructure, payment flows, systems under load Vibe-code your landing page. Craft your authentication system. Vibe-code your admin dashboard. Craft your data pipeline.

Great developers switch between modes. They vibe-code to move fast, then apply craft to the parts that matter. They know technical debt is fine if it's intentional and contained.

The companies building the future aren't choosing between vibes and craft. They're using both, strategically.

Where do you land? Are vibe-coding and AI enabled IDE's part of your toolbox?