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-up1138arrow-down11
arrow-up1137arrow-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-square15fedilink
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…
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…