Your critical systems are down. How do you decide which task to tackle first?

In a past internship, I got the advice to "stop the bleeding first." So, if I recently pushed code to production that might have caused this outage, I would revert to a version of the code that worked fine. Only after that would I investigate what the specific bug was and how to fix it.

System meltdown could be a scary experience for me, especially if it's the bread basket of the company I'm working for. When such a thing happens, I'd prioritize tasks. The first task would be to identify the issue affecting business-critical functions and address them with immediate effect. I would then focus on resolving the root cause of the outage rather than just temporary fixes. A quick assessment process helps determine the most critical issues to restore functionality as quickly as possible.