soyagi@yiffit.net to Science@lemmy.ml · 1 year agoVoyager 2: Nasa loses contact with record-breaking probe after sending wrong commandwww.bbc.comexternal-linkmessage-square15fedilinkarrow-up1137arrow-down11cross-posted to: worldnews@lemmit.onlinespace@lemmit.onlinespace@beehaw.org
arrow-up1136arrow-down1external-linkVoyager 2: Nasa loses contact with record-breaking probe after sending wrong commandwww.bbc.comsoyagi@yiffit.net to Science@lemmy.ml · 1 year agomessage-square15fedilinkcross-posted to: worldnews@lemmit.onlinespace@lemmit.onlinespace@beehaw.org
minus-squarethepineapplejumped@lemm.eelinkfedilinkarrow-up33·1 year agoWho hasn’t pushed bad code to production?
minus-squareBig P@feddit.uklinkfedilinkarrow-up17·1 year 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]@midwest.sociallinkfedilinkEnglisharrow-up3·1 year ago“lie down on floor try not to cry cry a lot”
minus-squareMalReynolds@slrpnk.netlinkfedilinkEnglisharrow-up2·1 year agoyeah, bad code to production, not so much, fix with SQL, uh huh…
minus-squareTiuku@sopuli.xyzcakelinkfedilinkarrow-up8·1 year agoI’d hate to be the person who was supposed to review it…
minus-squareStarkillerX42@lemmy.mllinkfedilinkarrow-up8arrow-down13·1 year 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