The phrase “vibe coding” has bothered me for some time.
It’s usually said with a smirk. Usually by experienced engineers.
And that was appropriate for a while. 2024-25 were full of crypto-bro levels of fanfare fuelled by big egos building small apps in days.
Most of that was hype was unwarranted.
But we're in 2026 now. The slow boil has reached us.
What is now possible with AI has evolved unimaginably.
We've moved past "vibes", yet the term “vibe coding” has stuck.
Empowerment isn't a "vibe"
To many, the term implies that what’s happening is casual. Loose. A founder waving at an LLM and hoping something compiles.
But “vibe” massively undersells what’s really going on.
For someone like me — not an engineer by training — being able to build working software isn’t about vibes. It’s about empowerment, velocity, momentum. It’s about user experience. It’s about customers and satisfaction.
Your product is a conversation with the market.
I first heard this quote from Des Traynor on the Cheeky Pint podcast with John Collison and it’s really stuck with me.
For years, the path from idea to implementation looked something like this:
Have an idea → explain it → write a spec → justify it → debate it → prioritise it → design it → refine it → debate it more → build it → test it → ship it → get feedback → repeat back to step 1.
Every step added latency. Not just time — cognitive drag. Social drag. Justification drag.
Not to mention, the very number of steps, the time consumed by passing through all these steps, and the very thought of even going through these steps, meant many ideas were never even attempted.
It may sound harsh, but I've seen it in so many teams: engineering is where good ideas go to die.
Now? If you're set up to embrace the world we're in, the journey is radically transformed:
Idea → build → test → refine → ship → improve.
And that is not a cycle that happens in months, weeks, or even days. It's a cycle that can happen in hours, if not minutes.
Speed of iteration isn’t a "vibe"
Forgive me for linking to another Stripe founder, but I have long found Patrick Collison's "Fast" page immensely inspiring: examples of people quickly accomplishing ambitious things together.
Iteration speed is leverage.
When building something new, the most valuable thing is rarely elegant code, a beautiful user interface, or following a set process or doing things in a certain way.
It’s really simple: all you really care about, to begin with, is whether the thing you are building is actually valuable.
Does this flow make sense?
Is this interaction clear?
Does this feature solve the actual problem the user has?
Before, for any product manager or designer or non-technical founder, exploring those questions meant being away from the product.
Drawing, writing, designing. You would do a lot of work in places that were not the actual

