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-square15fedilinkarrow-up1137arrow-down11cross-posted to: worldnews@lemmit.onlinespace@lemmy.worldspace@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 · 2 years agomessage-square15fedilinkcross-posted to: worldnews@lemmit.onlinespace@lemmy.worldspace@beehaw.org
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…
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…