So how do you address the points made in the GP post? Specifically, attacks, hardware failures, other issues that immediately impact customers? I assume that you don't wait until monday to address a failure that occurs thursday night, right?
When it comes to keeping the service running, there's always one person on call. We're really flexible on our team about hours, so if you need to do something on Saturday night you can cut out a little early a different day - honestly if you feel done for the day you can be done any day, but most of us are super driven and don't want to stop working when it's time. Despite the general 9-6 guideline we're not super formal about our hours.
Our support team also works a bit on the weekend (around 3 hours per day), and that's something we're working on fixing by adding to the team.
I work between 32 and 35 hours each week. I think about Treehouse a ton more (if I'm not asleep I've probably thought about Treehouse in the past couple of minutes), and answer email from time to time, but I don't know anyone who doesn't do that, and I usually get mean looks from my wife when I spend much time outside of my normal work hours answering email or playing around with code.
In general I don't think people on our team work more than 32-35 hours or so. One exception is our support team, and that's something we're working on remedying.
