You mean rewrite it all from scratch? If you have any kind of standards that is what you end up doing. If you know what you’re doing you do it right the first time and move on. Using AI for coding it like trying to train the most inept, inexperienced intern to ever walk the earth.
Comment on Vibe coding has turned senior devs into ‘AI babysitters,’ but they say it’s worth it | TechCrunch
victorz@lemmy.world 3 days agoBut surely you test the code and review it, right? That’s how you reinstate trust in what it outputs?
Disclaimer: I’ve never used AI to code, not even copilot.
BlameTheAntifa@lemmy.world 3 days ago
victorz@lemmy.world 2 days ago
That’s what I’m afraid of, and it doesn’t seem like employers are aware of this in general. Irks me especially as a consultant.
Serinus@lemmy.world 3 days ago
It’ll sometimes do dumb and/or redundant or too complicated shit. Pile up a couple of those and your codebase can get unmaintainable fast.
I find if you give it small chunks and keep an eye on it, it’s great.
I think one of my recent prompts was “Create a procedure that creates an example configuration file with placeholder values. If a config file doesn’t exist on start, give a warning and create the example config.”
It also works great as a replacement for an ORM.