137

submitted 1 year ago by [email protected] to c/[email protected]

15 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[-] [email protected] 33 points 1 year ago

Who hasn't pushed bad code to production?

[-] [email protected] 17 points 1 year ago

Imagine executing the command, immediately realising you fucked up and having to wait 36 hours for the response back from the probe

[-] [email protected] 12 points 1 year ago

"7373636272811891 rows affected"

Shit....

[-] [email protected] 3 points 1 year ago

"lie down on floor
try not to cry
cry a lot"

[-] [email protected] 2 points 1 year ago

yeah, bad code to production, not so much, fix with SQL, uh huh...

[-] [email protected] 7 points 1 year ago

It's always an intern doing this shit

[-] [email protected] 8 points 1 year ago

I'd hate to be the person who was supposed to review it..

[-] [email protected] -5 points 1 year ago

I've never pushed bad code to production. None of my unit tests fail*.

* I don't ever write unit tests

[-] [email protected] 2 points 1 year ago

We don't do that here

this post was submitted on 01 Aug 2023

137 points (99.3% liked)

Science

13013 readers

33 users here now

Subscribe to see new publications and popular science coverage of current research on your homepage

founded 5 years ago

MODERATORS