4 ms·
No I have to field a thousand questions about why nothing is working from just about every part of the organisation. Then spend several hours after it has recov
by uuyi 4y ago
No I have to field a thousand questions about why nothing is working from just about every part of the organisation. Then spend several hours after it has recovered assigning blame back to the engineers when they do something stupid rather than blaming it on the GitHub outage.
- mxuribe 4y agoIt reminds me of a time many years ago - before SaaS days - that a co-worker was similarly disrupted due to unreliability of a vendor system...and his anger towards internal senior staff for (what many obviously) considered to be a poor decision to go with said vendor. So my buddy was tempted to automate email forwards to a partiocular senior leader...so they somewhat feel the pain of all the messages being sent on a partoicular topic...plus my buddy acvited his email's out of office message to both assure folks that he was aware of the issue and to contact the senior leader most responsible for the poor vendor decision...again, to share the paion. Ultimately he didn't do that direct of a blame for fear of getting fired...but he did implement the out of office in a general fashion at least to lessen/avoid him having to answer questions about the numerous outages, etc. He didn't name any names...but some savvy folks in the org who understood the management hierarchy eventually figured things out and knew to start pionging that senior leader...and my friend didn't get fired...So there could be some mildly automated ways to lessen disruptions to your life. ;-)
- uuyi 4y agoUnfortunately the guy who decided this is gone. I should print and mail everything to him instead :)