they didn't say "surely everybody does" they said "safe to assume all", when really what they should have said is "safe to assume any" meaning any that you encounter and consider using.

I think it makes sense as a reasonable heuristic going forward, assume the MVP was vibe coded or nearly vibe coded (a weeks worth of human / agent work together, then initial release)

Claude Design was/is absolutely brilliant. The embedded skill in work and code is capable but the experience of Claude design was so much cleaner.

I don't know the answer. I suspect the answer today is yes for any "boxed" products like CLIs, desktop apps, mobile apps, simple client side apps, SDKs, etc. Complex services that have a livesite and deployment orchestration and numerous moving parts are still struggling, but everyone is pushing there too anyway.

As for users, I think it depends on the individual users. A lot of the time users abstract your software as a blackbox. It either works or it doesn't, and as long as you can fix it quickly and they get every bizarre feature ask answered quickly, that's all what some care about.

Personally, I have an all times low trust in the software I run. I used to cruise Show HN, /r/selfhosted, and GitHub Trending for cool new software to play with, learn from, or get inspired by. I don't anymore because I see what agents generate at work all day long.

There used to be this old joke among us programmers that we think it's insane that people trust their life to software when we all know how buggy it all can be. It was true, but also we knew that we can eventually get decent enough software. This is also out of the window now. Everything on all those places is a vibecoded thing generated in a couple of hours and no one knows what code is in there. It'll only get worse.

Sure they will. Case in point: Claude Code. I think its being vibe coded every afternoon, and indeed lots of programmers gladly take it with its various and often-changing quirks and small bugs. No biggie, it still gets the job done.

99% of people don't care, it's us programmers that are living in a bubble thinking that other people prioritize same stuff as we do. So yes, people won't care and will depend on someone's vibe coded apps, just like they use Windows, Adobe and whatnot even though those suck.

I don't really know what to say tbh. I feel insane at times too but I'm being a realist and a pragmatist. I think I'm in the "changed their mind" camp because I got tired of fighting and can't deny reality. It is a losing battle. All approaches to manage changes in a traditional way also don't work. I have seen people who left because they can and I might follow suit too.

Like I think (or know) code reviews are also over. Someone asks me for a 10-11am brainstorming meeting regarding a concept they are working on, at 11:15 they have a "design doc" ready, at 1pm they ping me if I had a chance to review it yet, at 3pm I approve it, at 3:30pm they send a 7k line PR... "dude, that's not ok. I'm not reviewing 7k line change" so they say "oh yes absolutely sorry about that. that makes a lot of sense. Do you want 7 1k-line PRs? or 14 500-line PRs?" "hey Claude, split this into 10 commits and open 10 stacked PRs" :|

This type of comments gives me the impression that HN is riddled with AI marketing bots.

Most people are practical

Reality is making you question your sanity.

The comments are just accurately describing that new, insane reality.

There was a generation of programmers who obsessed about memory alignment, bit packing, SoA vs AoS, memory arenas, handwritten assembly, etc. For well over a decade now, a todo app would take 800MB in RAM, but it has really cool mark-done animation so people would use it. If it's slow on your machine, get the new i7 or M58 mac to experience this awesome todo app.

Sort of, that's the mindset you get because you've no clue how the app actually works.

We have a 100% vibe-coding team, and yes, when they couldn't pass through the CI/CD at some point, they contacted the Ops team and literally said "the agent said the problem is on your side".

…yes? This is the equivalent of an electrician showing up to your house without tools.

It would be faster to setup a deepseek locally hosted instance or glm than try and build by hand, assuming all hosted providers were down somehow.

Which is to say, there is no token quota. If you run out you buy more.

How many times have you heard "we can't work because GitHub is down?". This has nothing to do with AI, and yes, it's commonplace.

Not to mention the "yes, there's a bug. We opened a ticket to the maintainer. Now we wait".

This reminded me my dad's story. "In highschool we used to tell our teachers we couldn't do our homework because lights were out." Take anyway you want.