Usually there’s a primary and a secondary. One person handles the actual debugging and the other handles the communication and coordinating. While I agree it’s

Usually there’s a primary and a secondary. One person handles the actual debugging and the other handles the communication and coordinating. While I agree it’s poor management to ask for an update every few minutes, it’s not because asking for an update is bad, rather because they themselves failed to communicate and train their employees to properly handle communication. Looking back, this was something we did in our team when I was just <2 years out of college. I was the secondary and posted updated to the tickets and emailed the team every 30 minutes. I was also the one calling in people to help when primary needed help. My manager didn’t bother us because he had already clearly laid out how we handle issues of each severity and who does what. It was also clear what the chain of escalation was and who and how to reach out. Incidentally, it was also my job to close the issue by identifying the cause and fixing the issue from recurring - because the secondary was only observing and communicating they get to see the bigger picture and also a welcome break for the person working hard to fix the issue. Learnt a lot by working with a team that knew how to handle themselves. And we weren’t SRE - just regular devs. This manager - my very first one - has also been the best one I’ve ever had. I wasn’t surprised at all when he quickly scaled the ladder and is doing really well for himself now.