The easier it becomes to build, the harder it becomes to ignore bad ideas
Vibe coding did not save us from stress
This is not my text - but I’ve seen it on Facebook and Facebook is shit at finding things again. I want to keep it here, so I can re-read it from time to time. Or maybe years from now.
The original post is here: https://www.facebook.com/story.php?story_fbid=28689760877298964&id=100000753011970&post_id=100000753011970_28689760877298964# — presumably the person who posted it is the real author.
Here it is:
Unfortunately, “vibe coding” didn’t solve the problem of “tech bros” not having time. It worsened it.
Before, they were busy because building software was hard. Now they are busy because building software has become too easy to start and too dangerous to stop.
One small idea that should have died peacefully in the notes app by 2:13am is now a “working MVP” before sunrise. By morning, they’ve already bought a domain, created a waitlist, opened a Telegram community, designed a logo that looks like every other tech startup logo, and posted on X that they are “building in public.”
What exactly are you building, sir?
Nobody knows.
Not even you.
But because AI wrote some code, connected some APIs, and produced a dashboard with suspicious confidence, you now feel morally obligated to keep going. What should have remained a random thought like “what if there was Uber for left-handed barbers” has now become a product roadmap, investor deck, and an emotional burden.
This is the problem.
Vibe coding did not free tech bros. It gave every passing thought the power to become a startup.
In the past, lack of technical skill used to protect people from nonsense. There were natural barriers. You needed patience, knowledge, structure, and sometimes a developer friend who would look at your idea and say, “This doesn’t make any sense.” That was mercy. That was divine intervention.
Now there is no gatekeeper.
You can wake up feeling unusually inspired after two cups of coffee and one podcast episode, open your laptop, type “build me a platform that revolutionizes human productivity using AI,” and within a few hours you are already in a serious relationship with a product nobody asked for.
And once it starts working small, peace disappears.
Because now you have users.
Maybe not plenty. Maybe just eleven confused early adopters and your cousin in Lekki. But users are users. One person is already complaining that the reset password link is not working. Another says the app crashes on Android. Somebody else is suggesting a feature that would require rebuilding everything from scratch. Now you are no longer just a man with an idea. You are a founder.
A stressed founder.
A founder who has not bathed.
A founder who is tweeting things like “sleep is optional when purpose is clear.”
Meanwhile your actual purpose was to rest.
Vibe coding has created a new category of suffering. People are no longer only overworked because of deadlines, bosses, or clients. They are overworked because their ideas now have access to electricity.
That is dangerous.
Every tech bro now has twenty unfinished apps, four half-baked SaaS products, three AI agents, two chrome extensions, and one landing page claiming to change the future of work. None of them is making money, but all of them are demanding updates.
So instead of having more time, they now spend their lives maintaining accidental businesses.
That is the irony.
The promise was speed.
The result is multiplication.
More products.
More bugs.
More false hope.
More screenshots.
More threads.
More “just shipped this.”
More silent panic.
Because the easier it becomes to build, the harder it becomes to ignore bad ideas.
And tech bros, unfortunately, are people with many bad ideas and unusual confidence.
Vibe coding did not save them from stress.
It simply removed the friction that used to protect them from themselves.
Let me go and “npm run build” my latest MVP.
Just one more deploy to main before I leave the office.
That was the original text as I’ve seen it and copy-pasted it here.
Personally, in addition to most of the bad traits described in it, I’ve also started to develop another one: since all that AI access is so expensive, it seems a shame to not keep it as busy as possible. But that’s even more f-ed up - am I supposed to align my schedule around Claude’s quota, rather than adapting it - the tool - to myself? There are better things in life than that.