[davidgay]

> It's a balance. You shouldn't routinely be working a ton of nights and weekends. But sometimes shit hits the fan at inconvenient hours and you need to respond. If not, you have to have routine 24/7 coverage which gets really expensive really fast ultimately leading to lower salaries for developers.

The not-uncommon answer to this is an oncall rotation, where you are paid at some fraction of your full-time salary, to respond to such problems.

The fraction likely works out better than 'overtime' pay, as it's for all the time you are oncall, not just when some issue occurs.

[ciceryadam]

Yup exactly, if I'm on emergency calls, I get payed 10% of my base hourly to be available, online in 15minutes and ready to solve issues. As soon as I get a call during this time, it's overtime (125% of hourly pay, bonuses for weekend/night calls). If I'm on holiday I'm out for the company, but I'm there for colleagues. With this system did daily rotations and weekly rotations, both lengths have their pros and cons.