re: What's your worst nightmare as a coder? VIEW POST


Production releases on a Friday evening ๐Ÿ˜


I think the goal should be to get to the place where this isn't a big deal. Testing in production should be a thing. That's not a trolling comment, and I'm dead serious.

Get to where you can deploy multiple times a day, every day, all day.

For reference, read stuff by Charity Majors about observability.


Thanks! We just happened to find a somewhat-critical error on Google Analytics and decided to pull the trigger ASAP to get it fixed. Shouldn't be too traumatic of a deploy :)


Hope you have some good CI/CD for that :-)

Yup! Jenkins rules :)

It didn't go as well as it could (some repo drama), but we managed to get stuff done. Yay!

Awesome! Late night deploys suck, we have to in some cases to reduce user downtime. We had to recently migrate an entire AWS VPN - business team was "shipping their pants". It went fine with minimal downtime. Which leads to a question, when should Developers NOT tell business about some changes? I have found that sometimes they make things worse off than they should be.


I think this heavily depends on the risk and impact of the deploy


I definitely agree with you here, but on Friday evenings people can often get distracted with weekend plans. Then if something goes wrong with a deployment, asking people to stay late and resolve the issues can be hard (for everyone involved).

This can be challenging, and its why our team generally tries to avoid this (but it does happen sometimes).


๐Ÿ˜†๐Ÿ˜†๐Ÿ˜†๐Ÿ˜†๐Ÿ˜† great


Don't forget, "when a critical resource is starting two weeks' PTO the next day".


That's bringing it to a whole other level ๐Ÿ˜‚


Been there, done that. Leave before they ask you to work weekends.


If they are asking, you don't need to say yes. If you need to get out the building before this, then they are not asking you, in which case you need to LEAVE THAT JOB!

code of conduct - report abuse