Any time you have worked long hours it is a sign of a broken process.
--------------------------
I see the point they're trying to make, but this is the problem with speaking in absolutes ...
My personal preference (and I suspect other developers do this too, but I could be very wrong about that) is to work when I'm in the zone ... sometimes I can go for 8 hours, others I can go 24 hours straight without any trouble (other times I don't get anything done for a couple of days) ... during projects when I'm knee deep in building something, its not uncommon for me to do 10 - 14 hour days ... not because its expected of me, but because that's how I work.
As long your employer isn't forcing you to do death marches/ insisting you work on weekends and you're getting good rest, exercise and eating well, I don't see a problem.
--------------------------
I see the point they're trying to make, but this is the problem with speaking in absolutes ...
My personal preference (and I suspect other developers do this too, but I could be very wrong about that) is to work when I'm in the zone ... sometimes I can go for 8 hours, others I can go 24 hours straight without any trouble (other times I don't get anything done for a couple of days) ... during projects when I'm knee deep in building something, its not uncommon for me to do 10 - 14 hour days ... not because its expected of me, but because that's how I work.
As long your employer isn't forcing you to do death marches/ insisting you work on weekends and you're getting good rest, exercise and eating well, I don't see a problem.