soyagi@yiffit.net to Science@lemmy.ml · 2 years agoVoyager 2: Nasa loses contact with record-breaking probe after sending wrong commandwww.bbc.comexternal-linkmessage-square15linkfedilinkarrow-up1139arrow-down11
arrow-up1138arrow-down1external-linkVoyager 2: Nasa loses contact with record-breaking probe after sending wrong commandwww.bbc.comsoyagi@yiffit.net to Science@lemmy.ml · 2 years agomessage-square15linkfedilink
minus-squarethepineapplejumped@lemm.eelinkfedilinkarrow-up33·2 years agoWho hasn’t pushed bad code to production?
minus-squareBig P@feddit.uklinkfedilinkarrow-up17·2 years agoImagine executing the command, immediately realising you fucked up and having to wait 36 hours for the response back from the probe
minus-squarevettnerk@lemmy.mllinkfedilinkarrow-up12·2 years ago“7373636272811891 rows affected” Shit…
minus-squareArgentCorvid [Iowa]@midwest.sociallinkfedilinkEnglisharrow-up3·2 years ago“lie down on floor try not to cry cry a lot”
minus-squareMalReynolds@slrpnk.netlinkfedilinkEnglisharrow-up2·2 years agoyeah, bad code to production, not so much, fix with SQL, uh huh…
minus-squarenutbiggums@lemmy.mllinkfedilinkarrow-up7·2 years agoIt’s always an intern doing this shit
minus-squareTiuku@sopuli.xyzlinkfedilinkarrow-up8·2 years agoI’d hate to be the person who was supposed to review it…
minus-squareStarkillerX42@lemmy.mllinkfedilinkarrow-up8arrow-down13·2 years 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