Question Guy (6/24/2013)
As I like to say, make your job what you want it to be. I want it to be 40 hours or so, therefore it is. Else I woulnd't have time for kids, workouts, and sports, and house projects. I didn't figure that out at my first job I worked at for 8 years, but at my current job that last 5 years, I dont think I've worked over 45 hours 1 week. We are severly short staffed in developers, me the only dba/developer, system admins, after hours support/help desk. But all is well, the company has been growing and making money for as long as I've been here.If not 40 hours at this job, them somewhere else. Its not like doing IT work is getting any easier, and long hours only gets you more long hours.
I've learnt that there is a certain amount of brass necking at managerial level. Pretend that something is more critical than it really is and that someone higher up the food chain has personally blessed it when they probably haven't.
One of the good things about implementing agile is that the team must be able to sustain the pace indefinitely which means that overtime is the exception rather than the rule. As DBAs can you honestly tell me that you can sustain 60 hour weeks at an intense pace? Personally, I put in 40+ hours but if I reach to 50+ then I'm not performing at my best. The extra hours are wasted hours and actually detract from my usual performance.
As a wise man once said "Render unto caesar what is due unto caesar...."