| ▲ | discreteevent 5 hours ago | |||||||||||||||||||||||||||||||
> AI works. For some definition of "works". This seems to be yours: > I'd go further and say vibe coding it up, testing the green case, and deploying it straight into the testing environment is good enough. The rest we can figure out during testing, or maybe you even have users willing to beta-test for you. > This way, while you're still on the understanding part and reasoning over the code, your competitor already shipped ten features, most of them working. > Ok, that was a provocative scenario. Still, nowadays I am not sure you even have to understand the code anymore. Maybe having a reasonable belief that it does work will be sufficient in some circumstances. | ||||||||||||||||||||||||||||||||
| ▲ | user34283 4 hours ago | parent [-] | |||||||||||||||||||||||||||||||
Yes, as I said, it is working well in my side project. The application works and I am happy with my results so far. It's interesting how this workflow appears to almost offend some users here. I get it, we all don't like sloppy code that does not work well or is not maintainable. I think some developers will need to learn to give control away rather than trying to understand every line of code in their project - depending of course on the environment and use case. Also worth to keep in mind that even if you think you understand all the code in your project - as far as that is even possible in larger projects with multiple developers - there are still bugs anyway. And a few months later, your memory might be fuzzy in any case. | ||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||