3 ms·
Being on call and in a constant state of readiness to troubleshoot problems is tiresome. Even if problems rarely occur, the constant awareness of potential res
by nugget 8y ago
Being on call and in a constant state of readiness to troubleshoot problems is tiresome. Even if problems rarely occur, the constant awareness of potential responsibility can quickly lead to burn out. The medical field has known this for a long time, and as a result, physicians get paid a lot of money to take extra call coverage. This is a very neglected topic of discussion within software development.
- rajeshmr 8y agoThis is a very important point but oft neglected too. I wish more people speak out about this.
- toomuchtodo 8y agoFormer ops engineer here. Get out of ops. In the current climate, it is rare you'll find a role that compensates you for being on call frequently and the toll it takes on you.
- dijit 8y agoThis a thousand times. Ops is undervalued and expected to deliver a lot in today’s workforce. You get better respect and compensation for SWE. I wouldn’t reccomend this career unless you’re unable to do software engineering.
- majormajor 8y agoA fair number of places have engineers do ops. It's bad in the long run for many reasons, but rarely do I see people ask about it at interview-time.
- MrMember 8y agoMan this one sucks. Being called at 2am to fix something once every couple of months isn't great but I can deal with it. Knowing I can be called at 2am on any day and be expected to fix something and not knowing when that will happen is what kills me. Despite the really good benefits in my current position I'm casually looking for a new job solely because of the on call schedule.