Login
You're viewing the mastodon.frost.kiwi public feed.
  • MiikkaMiikka@mastodon.social
    Oct 24, 2026, 4:58 AM

    I'm a habitual overthinker, yet incident response is not a problem. Incidents are also a golden opportunity to understand a complex system: you get to see the system in an unusual state and you get to poke it in a way that you usually wouldn't do.

    Would you overload your main database just to find out what happens? Probably not. What if your customers do it for you? Better cash in on the opportunity.

    💬 1🔄 0⭐ 1

Replies

  • MiikkaMiikka@mastodon.social
    Oct 24, 2026, 5:08 AM

    There's a school of thought that tries to bring incidents under control by using response protocols and runbooks.

    I'm not sure if it's very effective? It's good to have a standard for who responds to the incident and how they communicate and coördinate, but when it comes to solving the problem at hand, you've got to :toot: improvise :toot:

    💬 1🔄 0⭐ 1
  • MiikkaMiikka@mastodon.social
    Oct 24, 2026, 5:09 AM

    If your incident can be solved by an expert system, it should be solved by an expert system, not a human. And then we're back to thinking on our feet.

    💬 0🔄 0⭐ 0