Non of those examples are relevant.
Those examples are specific tools or specific implementation pattern, AI in development is a tool.
It doesn’t dictate how to write software or what the written code will look like, it’s a tool that speeds up your code wiring. It catches typos and silly bugs that take hours to debug, it’s able to generate useful unit tests, it can clean up and apply my code style way better than codemaid or resharper ever code, it’s taken care of so much tedious shit and made software development fun again.
Vibe coding is not the future of development. If you aren’t learning to use AI as a tool in development, you are going to be left behind.
It’s more apt to compare it to IDEs. Sure, you can still write you entire app in vim and compile it in the terminal, but you would have been very foolish to deny the future of development was in IDEs.
Real world development isn’t creating exciting apps all the time, it’s writing the same exact boring convention based code sticking to an established pattern.
It can be really boring and unchallenging to create your millionth respiratory, or you can prompt your ide to create a new repo and with one sentence it will create stub out 10 minutes worth of tedious prep work. It makes programming fun again.
In one prompt, it can look at my finished code and stub out half decent documentation that otherwise wouldn’t have been completed at. It does hallucinate sometimes, or it completely misunderstands the code, so you have to correct a few sentences, but the brain drain of coming to with the sentence structure to write useful documentation is completely lifted, and the code is now well documented.
AI programming is more than just vibe coding, and it’s way more useful than everyone here insists it’s not.