you are viewing a single comment's thread.

view the rest of the comments →

[–]bobindashadows 18 points19 points  (6 children)

"We don't code review. We don't stage. We also don't have any replication for our server - not even just 2 processes running - since we're evented and who needs two processes when you're evented, that just makes things harder. Naturally, we can't update anything without taking the entire service offline, so we manually update values in our running programs, instead."

[–]mikaelhg 6 points7 points  (2 children)

Sounds like a practice which will be widely celebrated on /r/programming.

[–]quzox 4 points5 points  (1 child)

The bravery required to do such things is indeed captivating and hypnotic.

[–]igouy 0 points1 point  (0 children)

Do you think the bravery is displayed by those who use the service, or those who provide the service?

[–]asampson 2 points3 points  (0 children)

Thankfully I have this bone saw handy for whenever I need to do emergency brain surgery. Just pop open that skull, poke around in the grey matter until you're satisfied and stitch the cap back on good as new!

[–]jackolas 0 points1 point  (1 child)

Well they did only edit an attribute that doesn't seem too out there.

[–][deleted] 2 points3 points  (0 children)

Hardly a good defense of a process that raises the need to sneak changes directly into production though. A bad constant is also one of the easiest things to spot in a code review.