DEV Community

Discussion on: How I Stopped On Call Support

Collapse
 
cchana profile image
Charanjit Chana

The idea of having someone 'on call' in the team I lead was floated but it never came to that. Perhaps we were lucky with the geographic location of our customers that they found issues during the day that we could resolve then and there for them.

But ultimately, we really improved our standing by introducing much better code coverage (long overdue), we had extensive regression tests which meant if we hadn't taken the responsibility during planning, development, testing or review then we could flag it as something that should be improved... did that always work? Not enough.

In a job long ago, we rotated and I only ever got called once about a project I knew nothing about! We managed to identify when we could roll back to and took care of it the next day.

Looking to the future and putting myself in the shoes of a manager/lead again, I'm thinking that this is a good strategy for giving focus to the issue. If these calls are rare, perhaps it's OK to carry on as you are but if this is a daily/weekly thing then it definitely needs addressing. I'll need to think about it some more, perhaps over a Manhattan or two, but it's something I will seriously consider implementing myself.