A lot of more senior coders when they actively try vibe coding a greenfield project find that it does actually work. But only for the first ~10kloc. After that the AI, no matter how well you try to prompt it, will start to destroy existing features accidentally, will add unnecessary convoluted logic to the code, will leave benhind dead code, add random traces "for backwards compatibility", will avoid doing the correct thing as "it is too big of a refactor", doesn't understand that the dev database is not the prod database and avoids migrations. And so forth.

I've got 10+ years of coding experience, I am an AI advocate, but not vibe coding. AI is a great tool to help with the boring bits, using it to initialize files, help figure out various approaches, as a first pass code reviewer, helping with configuring, those things all work well.

But full-on replacing coders? It's not there yet. Will require an order of magnitude more improvement.

If you look at his github you can see he is in the first week of giving into the vibes. The first week always leads to the person making absurd claims about productivity.

To be fair, AI probably wrote the blog post from a short prompt, which would explain the lack of detail.

Specifics on the setup. Specifics on the projects.

SHOW ME THE MONEY!!!

>Somehow 90% of these posts don't actually link to the amazing projects that their author is supposedly building with AI.

Maybe they don't feel like sharing yet another half working Javascript Sudoku Solver or yet another half working AI tool no one will ever use?

Probably they feel amazed about what they accomplished but they feel the public won't feel the same.

AI is great, harness don't matter (I just use codex). Use state of the art models.

GPT-5.2 fixed my hanging WiFi driver: https://gist.github.com/lostmsu/a0cdd213676223fc7669726b3a24...