> I have seen that once I start spending a lot of time coding/in front of the computer, my efficiency (amount of work down per hour) goes down. In addition to

> I have seen that once I start spending a lot of time coding/in front of the computer, my efficiency (amount of work down per hour) goes down. In addition to decreasing efficiency at code-production (ie fewer lines being written), the major killer with tired coding is that adrenaline takes over and you get into 'go mode'... suddenly you're punching out widgets and no longer stopping to question your approach. It's doubly bad because that kind of work tends to mate with deadlines to create higher stress and a feeling of having no time to try out alternatives... Head down and plowing though is a good approach to some problems sometimes. But for IT work? There's a good chance that OT work isn't just poor quality and slow, but also contains a lot of unnecessary effort that never needed to be done at all. A good Engineer will solve your problem in 5 days. A great Engineer will spend 4 days figuring out how to solve your problem in 1... A tired Engineer under a deadline will work a 110 hour week cranking out a half-assed bare-minimum solution only to find it replaced in less than 10 hours by someone who was awake enough to consider some alternatives and needed something that worked :/