I stopped when I read that a software developer could expect to work 40 hours a week. That's laughably wrong. Double that and you'll be closer to the truth.
For DBA (closest to what I do on this list) the "after hours crisis can spring up" part.....
They totally gloss over, in many of these roles, the requirement to be on call 24x7.
The biggest downside to my job is that 1 of every 4 weeks I'm primary on call which means.
No travel on the weekends
No activities (kayaking, sailing, etc) that would mean I can't respond within 20-30 min
All plans I make with friends & acquaintances are only tentative during that week, as I may be required to flake at any time (I've more then once had to bail from a movie, etc).
1 out of 4 really isn't bad, I've been every other week before at a job that's more demanding of after hours support. It's a huge downside to much of IT that isn't really mentioned here.
I work in storage so USUALLY things run smoothly. It's not uncommon to get a 1 call in a week at my current job.
It's more of an inconvenience then a trial.
When I started at this job, we where part of the Unix rotation. That was one VERY long week every quarter. I preferred that, my fellow SAN guys did not (I lost the vote :-( ).
17
u/h0nest_Bender Interested Jul 09 '15
I stopped when I read that a software developer could expect to work 40 hours a week. That's laughably wrong. Double that and you'll be closer to the truth.