▲ 138 ▼ Voyager 2: Nasa loses contact with record-breaking probe after sending wrong command (www.bbc.com) submitted 3 years ago by soyagi@yiffit.net to c/science@lemmy.ml 15 comments fedilink hide all child comments
[–] thepineapplejumped@lemm.ee 33 points 3 years ago (3 children) Who hasn't pushed bad code to production? permalink fedilink source hideshow 6 child comments replies: [–] peter@feddit.uk 17 points 3 years ago (1 child) Imagine executing the command, immediately realising you fucked up and having to wait 36 hours for the response back from the probe permalink fedilink source parent hideshow 2 child comments replies: [–] vettnerk@lemmy.ml 12 points 3 years ago (2 children) "7373636272811891 rows affected" Shit.... permalink fedilink source parent hideshow 4 child comments replies: [–] argentcorvid@midwest.social 3 points 3 years ago "lie down on floor try not to cry cry a lot" permalink fedilink source parent [–] MalReynolds@slrpnk.net 2 points 3 years ago yeah, bad code to production, not so much, fix with SQL, uh huh... permalink fedilink source parent [–] nutbiggums@lemmy.ml 7 points 3 years ago (1 child) It's always an intern doing this shit permalink fedilink source parent hideshow 2 child comments replies: [–] Tiuku@sopuli.xyz 8 points 3 years ago I'd hate to be the person who was supposed to review it.. permalink fedilink source parent [–] StarkillerX42@lemmy.ml -5 points 3 years ago (1 child) I've never pushed bad code to production. None of my unit tests fail*. * I don't ever write unit tests permalink fedilink source parent hideshow 2 child comments replies: [–] thepineapplejumped@lemm.ee 2 points 3 years ago We don't do that here permalink fedilink source parent
[–] peter@feddit.uk 17 points 3 years ago (1 child) Imagine executing the command, immediately realising you fucked up and having to wait 36 hours for the response back from the probe permalink fedilink source parent hideshow 2 child comments replies: [–] vettnerk@lemmy.ml 12 points 3 years ago (2 children) "7373636272811891 rows affected" Shit.... permalink fedilink source parent hideshow 4 child comments replies: [–] argentcorvid@midwest.social 3 points 3 years ago "lie down on floor try not to cry cry a lot" permalink fedilink source parent [–] MalReynolds@slrpnk.net 2 points 3 years ago yeah, bad code to production, not so much, fix with SQL, uh huh... permalink fedilink source parent
[–] vettnerk@lemmy.ml 12 points 3 years ago (2 children) "7373636272811891 rows affected" Shit.... permalink fedilink source parent hideshow 4 child comments replies: [–] argentcorvid@midwest.social 3 points 3 years ago "lie down on floor try not to cry cry a lot" permalink fedilink source parent [–] MalReynolds@slrpnk.net 2 points 3 years ago yeah, bad code to production, not so much, fix with SQL, uh huh... permalink fedilink source parent
[–] argentcorvid@midwest.social 3 points 3 years ago "lie down on floor try not to cry cry a lot" permalink fedilink source parent
[–] MalReynolds@slrpnk.net 2 points 3 years ago yeah, bad code to production, not so much, fix with SQL, uh huh... permalink fedilink source parent
[–] nutbiggums@lemmy.ml 7 points 3 years ago (1 child) It's always an intern doing this shit permalink fedilink source parent hideshow 2 child comments replies: [–] Tiuku@sopuli.xyz 8 points 3 years ago I'd hate to be the person who was supposed to review it.. permalink fedilink source parent
[–] Tiuku@sopuli.xyz 8 points 3 years ago I'd hate to be the person who was supposed to review it.. permalink fedilink source parent
[–] StarkillerX42@lemmy.ml -5 points 3 years ago (1 child) I've never pushed bad code to production. None of my unit tests fail*. * I don't ever write unit tests permalink fedilink source parent hideshow 2 child comments replies: [–] thepineapplejumped@lemm.ee 2 points 3 years ago We don't do that here permalink fedilink source parent
[–] thepineapplejumped@lemm.ee 2 points 3 years ago We don't do that here permalink fedilink source parent