Re:Team Structure for Software Reliability Within Organizations
by test1235 on Monday February 17, 2020 @09:19AM
(#22347837)
Did everyone get paid more to take on these responsibilities? I feel we're about to go through exactly the same thing at my company.
[ Parent
| on HN ]
Re:Team Structure for Software Reliability Within Organizations
by sokoloff on Monday February 17, 2020 @10:43AM
(#22348437)
We’re many years down the road, so we’ve mostly baked it into job descriptions and expectations at this point. In some geographies, we’ve had to craft those responsibilities and pay/comp time philosophies in specific ways to comply with local laws. In others where the law is silent, we’ve taken a laxer “if you got crushed by off-hours work, take appropriate comp time”.
During the old days of “you commit code and ops runs it” and during transition to “you build and run it”, we did have some bonuses for being on-call or doing stints in problem management. Now, we bake that expectation into base salary except in locales where we have to split it out to comply with local laws.
Along the way, we've given enough merit increases, market adjustments, and promotions that it's impossible to say whether we had a bump specifically because of the industry's new philosophy on ops. If you wanted to make the case that we did, you could. If you wanted to make the case that we didn't, you equally could.
Re:Team Structure for Software Reliability Within Organizations
by sethammons on Monday February 17, 2020 @09:46AM
(#22347982)
The logic was that we are highly paid developers and are expected to build robust, reliable software with high availability. Typically a brutal on call night yields untracked time off.