2 ms·
Yeah this article didn't go where I expected it to go. Silence is nearly always an indication that someone is doing something or thinking about something, and t
by sanderjd 3y ago
Yeah this article didn't go where I expected it to go. Silence is nearly always an indication that someone is doing something or thinking about something, and the advice here is to interrupt them?
- mlrtime 3y agoBut how do you know that without any other information? In a high stakes incident you cannot let radio silence go off without clear communication on status updates... this was called out in the bottom.
- sanderjd 3y agoYou train people, delegate to them, and then trust them to do the right thing. This is discussed in the article as well, but I think expectations are much better than interruptions. And even then, it is better to set those expectations during training rather than during the response. People should be trained to prioritize communication during a response, but not above their work doing the response. And the people doing the work are individually best suited to make the call of whether what they're doing is more or less important than communicating. In my view, it's really hard to overstate how hard it is to be reading big volumes of logs, reconstructing the runtime state of some big complex distributed system from the breadcrumbs available, and thinking about what to do next to most quickly mitigate or get more information on the issue, while being bombarded with messages.