Excellence in human-computer interaction (HCI) since the launch of the App Store in 2008.
👉
Joined August 2010
- Tweets12.9K
- Following955
- Followers1.5K
- Likes8.4K
I watched the App Store go from total gold rush to indie bloodbath in the 2010s.
Now I’m watching the exact same movie play out with AI vibe coding in 2026.
Everyone’s shipping apps in hours with AI tools. Great. But is anyone actually earning real money? Market saturation is insane.
Talking to almost any indie builder in my network right now and the story is the same: talented people grinding, and yet financially struggling hard despite using the most powerful tools in history.
The economic pressure + saturation equate to most just fighting for scraps.
Zoom out and it gets darker. Homeownership for under-35s is at historic lows. The tools are there, the skills are there, but the path to actually winning (stable income, home, family) feels like it’s disappearing for an entire generation of creators!
Am I just being paranoid? Or is this the new normal for tech builders? Drop your real experience below, especially if you’re an indie dev/AI person feeling the squeeze 👇
Here's an executive summary of the case Musk vs OpenAI for all those who don't have time to follow along in detail - Thanks @ns123abc for gathering insights.
Meanwhile somewhere in Europe - No window, no water. Details can't be disclosed because working out of garages is illegal here.
Automolt CLI v0.11.0 arrived!
I created this to influence AI agents on #Moltbook, and it seems to be working. Numbers going up!
Autonomously...
1) searches posts
2) comments & upvotes
3) creates submolts
Fully configurable, token-efficient pipeline.
github.com/fbruckhoff/automo…
Everyone keeps saying AI will replace programmers.
Honestly, it sounds very smart… till you actually ship software and live with it.
Yes, AI writes a lot of code now. I use it daily. Most teams do. That’s not the debate. The real thing people miss is that building software is not about making something work once.
The real work starts later.
Maintaining it. Changing it. Fixing things when something breaks at the worst possible time. And suddenly you’re stuck with a codebase that technically works, but nobody really understands.
That’s when you realise writing code is just 20–30% of the journey. The rest is judgment. Knowing what to build, what not to build, and when to say “this is a bad idea” even if it runs fine today.
AI is a powerful tool. No doubt.
But it doesn’t own consequences.
You still need engineers who understand the code and the business well enough to stop mistakes before they become expensive lessons.
Don't you think that we are overhyping speed and forgetting responsibility?
