Late Night Updates
Pretty sure this has been mentioned on here before but it was fun…
Myself as Snr Dev and top server admin colleague and good mate based remotely were set for a late Saturday shift implementing major updates to our client facing service - code updates and associated db changes, an all-done or complete rollback scenario. Once MoTD was done we messaged each other and agreed we were good to go. M'colleague politely asked if I had a drink - obviously yes, a glass of red. How about you? I enquired. Small whiskey came the reply. I should add this was about 15 years ago, we had our phones on chatting to each other, Messenger for confirming specifics and a hop skip & a jump to pass any configs that were likely to lose something being copied at one end or the other due to it not being possible to copy text from my Windows session to one of the servers.
We set to it; steady, cautious, check, recheck, tick off the checklist as we went, confirm good, continue. It took longer than anticipated and the glass of red in front me wasn’t the first out of the bottle that night. By midnight the bottle was empty and we still had a way to go. I excused myself for a loo break and on returning got a suggestion to open another bottle - there was as I said a fair way still to go. So i did, and his whiskey consumption continued at its steady pace.
By 3 a.m. we were done - updates, 2nd bottle, scotch. Sanity checks showed all was well with the system and we agreed to reconvene at 11 to check and recheck to give us time to back it out by Monday if necessary. It was fine, although colleague and myself were a bit less so.
Monday morning came with plaudits from all sides - mgmt, clients & colleagues alike, for a job well done. Only one person became aware of the shenanigans a while after the event and she had the decency to keep schtum about it bless her. Happy days, but with hindsight it was a chuffing nuts idea.