4 ms·
So who should support emergency issues? Nobody?
by AndrewKemendo 10y ago
So who should support emergency issues? Nobody?
- hiou 10y agoThe same people who do this is other industries. Paid staff scheduled to work those hours. Honest question: You didn't know that?
- q3k 10y agoHow does being on pager duty not coincide with being paid to work these hours?
- CodeMage 10y agoThere is at least one big company out there, where every dev is part of what they call the "on call rotation" -- where being "on call" typically means being on pager duty -- without any special compensation for that. The only exemption is if you're working on a project that isn't yet in production. They tell you about it during their recruitment process and they communicate it very clearly: take it or leave it, there are no special cases. It sucks, but a lot of people take it anyway.
- greedo 10y agoYup. We're on call for a week at a time. Only compensation is the "privilege" of working from home on the Friday of the week we're on call. No extra pay, no comp time, nada. Luckily the number of calls is very low, maybe 1-2 per week.
- AndrewKemendo 10y agoAnother poster answered the question but your honest question isn't that honest. DevOps is paid for emergency ops - it's part of the job description.
- hiou 10y agoAnything in the world can be part of a job description. That speaks nothing about if it is reasonable or ethical. Many, many, many industries have overnight staff to handle these issues, but likely because software engineers tend to be young, lack a union and are paid salary with no overtime compensation, it is somehow acceptable in this industry. Which is why I honestly asked that question. Why do you and the above poster, find it so normal to be on pager duty when so many other industries, often with much more critical services, do not require it?
- AndrewKemendo 10y agoWhy do you, and the above poster, find it so normal to be on page duty when so many other industries, often with much more critical services, do not require it. False premise. Many jobs require it, including low paid ones across many industries. Many of my jobs which were not in IT required it sometimes (like working at a golf course and being called out for a jammed golf cart garage door in one case - which I clocked hours for btw). If it's part of your job description and the salary you get covers it then I'm not seeing why you should "find a different job."
- douche 10y agoReal industries that run 24-hours a day and have to be up all the time, run three shifts, they don't screw their day-shift into having to be available at the drop of a hat to cover. They also pay significant overtime multipliers when they do have to call somebody in outside of their scheduled hours.
- toomuchtodo 10y ago> If it's part of your job description and the salary you get covers it then I'm not seeing why you should "find a different job." Two reasons: 1. Your salary doesn't cover night and weekend pages in most first world countries regarding labor law (the US is backwards in this regard, but luckily the economy does well enough at the moment jobs are a plenty). 2. Quality of life. If your job requires on call rotation, interrupting your off-work hours or your sleep, and you're not getting paid enough (<$100K/year), immediately start seeking out another job. It's a sellers market.
- protomyth 10y agoIf you're running 24 hours then you should staff for that. If I work my 8 to 10 hours and then have to work another 2 or 3, it tends to wear one down. Ideally, there would be a financial incentive to fix production bugs so businesses aren't waking up developers. This isn't true when you have exempt employees (US term for no paid overtime) doing your support. I've seen manager go totally friggin stupid with employees who went above and beyond[2]. I still think some managers think we would "code ourselves a mini van"[1] if they paid us for support. 1) http://dilbert.com/strip/1995-11-13 http://dilbert.com/strip/1995-11-13 2) https://news.ycombinator.com/item?id=3015969 https://news.ycombinator.com/item?id=3015969
- AndrewKemendo 10y agoIf you're running 24 hours then you should staff for that. Right, so what's the problem? The original article isn't talking about putting people who aren't paid for pager duty on pager duty. The OP is whining about the mere idea of it and suggesting that if you have that job you should quit.
- jrockway 10y agoI really don't like the model of throwing support over the wall to some team that didn't write the software. There is no incentive to improve the software under those circumstances, and the people that get paged aren't in the position to fix what's broken. If you can fix the problem at 3am without thinking, then so can a computer program. Write that computer program.
- hiou 10y ago> There is no incentive to improve the software under those circumstances Classy. This comment is 100% exactly the attitude. This is why Step 1 is to find a new job. This poster is punishing you like a parent would a child. Is this the way you want to be looked at and treated? Did you study as hard as you did and spent so much time developing your craft for this? There are better opportunities out there. 1,000s of them. Avoid the jrockways of the world and you will have a much happier career and life.