All Software Developers and Engineers should get into Vibe Coding

Put away your pitchforks and hear me out.

I gave a talk about Vibe Coding and how to do it, targeting people who had never built a piece of software in their lives. However, three separate developers approached me about one thing I had said:

Sometimes vibe coding is a way to get an idea out of your head that might not be the final version, but a quick way to answer “is this thing worth it to spend my time, effort, and money on?”

They questioned me on this because I mentioned how I use vibe coding to help write scope for my teams. I might be unsure of a particular user flow—for example, a user uploads a document and the system asks if they want to add it to a collection—but vibe coding helps me build and tinker with the implementation.

These developers wanted to find out how to get their ideas into the world but were stuck on what the user flow even needed to look like. Specifically, I had given them the verbiage to articulate the barrier they were experiencing. In a nutshell:

“I’m stuck in a loop: I don’t build because I lack clear user flows, but I can’t define those flows because I haven’t built anything to learn from.”

Vibe coding breaks that cycle. Therefore, all developers and engineers should get into vibe coding.

If you’re still not convinced, here is a ten-minute exercise:

• List every project idea you didn’t build.

• Write a sentence for each one explaining why you didn’t build it.

• Ask yourself why again... and again.

I promise you that nine times out of ten, the reason will be some version of “I couldn’t build a vision around the user experience.”