Voyager 2: Nasa loses contact with record-breaking probe after sending wrong command
Voyager 2: Nasa loses contact with record-breaking probe after sending wrong command
The space agency is listening for any peep of the probe, which has been exploring space since 1977.
You're viewing a single thread.
Who hasn't pushed bad code to production?
33 0 ReplyImagine executing the command, immediately realising you fucked up and having to wait 36 hours for the response back from the probe
17 0 Reply"7373636272811891 rows affected"
Shit....
12 0 Reply"lie down on floor
try not to cry
cry a lot"3 0 Replyyeah, bad code to production, not so much, fix with SQL, uh huh...
2 0 Reply
It's always an intern doing this shit
7 0 ReplyI'd hate to be the person who was supposed to review it..
8 0 Reply
I've never pushed bad code to production. None of my unit tests fail*.
* I don't ever write unit tests
8 13 ReplyWe don't do that here
2 0 Reply