Pretty much.
I’ve started using AI on a project last week and the first thing I do is write tests. Lots of tests.
With enough guardrails, you could actually get pretty decent quality output out of it and with enough regression tests, you can ensure that nothing’s actually breaking.
Similarly, reviewing its changes and actually reading the code that’s being generated to ensure correctness is necessary. However, I am finding ways to automate that and reduce the incident rate of problems to even lower than my co-workers.
Jhex@lemmy.world 2 weeks ago
that’s nowhere near enough testing for such a large change… special one written by the slop machine
NoFun4You@lemmy.world 2 weeks ago
Creds?
riccardo@lemmy.ml 2 weeks ago
At my company we have been using AI very heavily to write code lately, and if that sentence was used to justify a 10k+ diff, whoever wrote it/vetted the change would have their access to the codebase revoked
NoFun4You@lemmy.world 2 weeks ago
So just one cred, I would think weeks of testing could cover things lol