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.
5 Comments
PattyMcB@lemmy.world · 41 pts · 1y
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.
theherk@lemmy.world · 11 pts · 1y
They should have used all caps. Then it would have listened. Oh wait…
sugar_in_your_tea@sh.itjust.works · 11 pts · 1y
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.
SpiffyPotato@feddit.uk · 2 pts · 1y
The second one is a testament to why you should always run it as a
SELECTstatement first to verify you typed it correctly.ZephyrXero@lemmy.world · 10 pts · 1y
And this is why there should always be a human in the loop for QA despite how many tests you have.