3 ms·
I think you just need to find a company where devs do not do oncall. Companies that have a dedicated "production support" team or something similarly named that
by DarrenDev 4y ago
I think you just need to find a company where devs do not do oncall. Companies that have a dedicated "production support" team or something similarly named that handle maintaining production environments.
I've worked for a dozen different companies (contractor) over the past 10 years as a backend engineer and have never been faced with oncall. Neither have my permanent employee colleagues. In many cases we had no direct access to production environments as that was managed by separate teams. In the one startup I worked at, it was so early stage that there were only ever a half dozen users, and the CTO handled any issues that popped up over the weekend.
The type of companies that had dedicated teams for maintaining live environments included big banks, government departments, insurance companies, large healthcare companies.
- Olphs 4y ago>dedicated "production support" team That's interesting, so if some bug pops up during the weekend they will just revert back? And then that bug gets handled later. Or is there also so rigorous QA process that bugs rarely happen, and it's more like infra issues that the "product support" team can handle on their own? The interesting part is that I think on-call is not only about infra issues etc., but could also be bugs in the application or some other weird behavior, which I'm assuming the "production support" wouldn't know how to handle. Maybe there is some huge amount of process to handle all that I'm just oblivious of, never having heard of this before?