Definitions do matter.
Regardless of where you sit on the (generative) AI fence, it’s safe to say that in 2025, the most loved, hated and debated term in Engineering is “vibe-coding”.
Everyone from clueless consultants to well respected thespians of the the trade, have used and abused this term.
But I have a feeling that most of the time, “vibe-coding” simply means prototyping.
While the former is a invite to a bitter debate, the latter is a well understood and respected act. If you don’t agree, let me show you.
How does the following post make you feel?
Hey, I vibe-coded a SaaS billing platform over the weekend.
For me, I immediately see the Process Manager or CEO in the person’s bio and think “yeah, good luck exposing all your secrets in production, you clueless moron”.
Now how about the following one.
Hey, I prototyped a SaaS billing platform over the weekend.
I’d generally lean towards, “Oh looks cool, let me try that out” or “Nice work. Do you plan to take it to production?”
See how one change of the word changed the meaning and how you feel.
Since we are entering a new year, I’d like to propose prototyping as a healtier alternative in engineering conversations, and I hope it finds it’s way in your New Year’s resolutions.