That fun moment when your A+ dev team deploys something to prod but not your lab. You attempt to deploy to the lab and Jenkins just stares at you and laughs, so you manually pull the files and config from prod and it fails to boot in your lab 
Oh and the dev team is on the other side of the planet, so they’re very asleep right now
Side note. I’ve told the offshore team that the dev pipeline has been broken for TWO WEEKS now and I got nothing but crickets. I love it so much 
Hey! We finally mostly fixed them! Only took 3 of us FOUR HOURS to fix two devices. For an update that should have taken about 20 minutes
(Note. The deployment pipeline is still broken. We manually configured them. And they still error on boot but if you hit retry it boots so WERE CALLING IT A WIN)
@puzzler995 wait so they’ve just been yeeting in prod?
@Damekraft I think they’re testing in their offshore lab. But yeah pretty much
@puzzler995 @Damekraft When someone says we tested in our lab I already know they pushed to production and turned off error reporting.
@Damekraft @randominternetuser … we’re not even gonna talk about that time where my director was making live changes to a bundle in a proof of concept store in prod to fix bugs before we showed off the POC 
@puzzler995 @randominternetuser oh nooooz as a director of platform engineering myself I don’t even allow myself anywhere near prod and I’m a huge pain in the butt about deployment state maintenance…
@Damekraft @puzzler995 Deploying to prod just means changing the backend IP in the reverse proxy to that of the dev server.
@randominternetuser @puzzler995 my spinnaker system cries out in sorrow lol
@randominternetuser @puzzler995 my entire career in cybersecurity melts into heat death
@puzzler995 losing idempotence is never fun…ugh
@puzzler995 Hack their phone emergency alerts
@MiaWinter if it was a prod issue I could, instead I just look like a moron to some on-shore devs looking to test their updates