They should have used all caps. Then it would have listened. Oh wait…
ZephyrXero@lemmy.world
on 22 Jul 02:16
nextcollapse
And this is why there should always be a human in the loop for QA despite how many tests you have.
sugar_in_your_tea@sh.itjust.works
on 22 Jul 02:44
collapse
showed it to senior folks who said the results looked fine
Did anyone look at the code?
Also, what’s a “multi-type”? Does he mean he needed to check a different field? Or are they doing something unholy without real schemas and got burned because they’re mess confused someone! Also, why is a junior being moved between teams and touching production immediately?
I have so many questions.
The second one makes a ton more sense, and is pretty hilarious.
threaded - newest
At least it wasn’t an AI agent that did it despite being told not to, repeatedly. And then refusing to restore from backups because they didn’t exist.
They should have used all caps. Then it would have listened. Oh wait…
And this is why there should always be a human in the loop for QA despite how many tests you have.
Did anyone look at the code?
Also, what’s a “multi-type”? Does he mean he needed to check a different field? Or are they doing something unholy without real schemas and got burned because they’re mess confused someone! Also, why is a junior being moved between teams and touching production immediately?
I have so many questions.
The second one makes a ton more sense, and is pretty hilarious.