@soyagi to [email protected] • 11 months agoVoyager 2: Nasa loses contact with record-breaking probe after sending wrong commandwww.bbc.comexternal-linkmessage-square15fedilinkarrow-up1150arrow-down11cross-posted to: [email protected][email protected]
arrow-up1149arrow-down1external-linkVoyager 2: Nasa loses contact with record-breaking probe after sending wrong commandwww.bbc.com@soyagi to [email protected] • 11 months agomessage-square15fedilinkcross-posted to: [email protected][email protected]
minus-squareBig Plinkfedilink17•11 months agoImagine executing the command, immediately realising you fucked up and having to wait 36 hours for the response back from the probe
minus-squareArgentCorvid [Iowa]linkfedilinkEnglish3•11 months ago“lie down on floor try not to cry cry a lot”
minus-square@[email protected]linkfedilinkEnglish2•11 months agoyeah, bad code to production, not so much, fix with SQL, uh huh…
minus-square@[email protected]linkfedilink8•11 months agoI’d hate to be the person who was supposed to review it…
minus-square@[email protected]linkfedilink-5•11 months agoI’ve never pushed bad code to production. None of my unit tests fail*. * I don’t ever write unit tests
Who hasn’t pushed bad code to production?
Imagine executing the command, immediately realising you fucked up and having to wait 36 hours for the response back from the probe
“7373636272811891 rows affected”
Shit…
“lie down on floor
try not to cry
cry a lot”
yeah, bad code to production, not so much, fix with SQL, uh huh…
It’s always an intern doing this shit
I’d hate to be the person who was supposed to review it…
I’ve never pushed bad code to production. None of my unit tests fail*.
* I don’t ever write unit tests