I mean, this is a light-hearted meme, no offense to the people actually fixing things.
But at a company like GitHub the first status update should be and probably is created semi-automatic (just approved by a human). Afterwards they should follow a process to assign an incident communication lead, who takes over all communication so that the rest of the team can work on fixing the incident.
@GitHub: Hire me for more incident response tips from the backseat! :P
Maybe because people were busy trying to fix it instead of writing announcements?
I mean, this is a light-hearted meme, no offense to the people actually fixing things.
But at a company like GitHub the first status update should be and probably is created semi-automatic (just approved by a human). Afterwards they should follow a process to assign an incident communication lead, who takes over all communication so that the rest of the team can work on fixing the incident.
@GitHub: Hire me for more incident response tips from the backseat! :P
At this point, you’d think github has had enough meetings about what to do when shit hits the fan.
Well, it’s a Microsoft company. So… ya know, they have shit hit the fan so often they would just be in meeting permanently.