[walkon]

Hours worked doesn't always contribute to burnout. I can easily feel burnout working 40 hour weeks filled with unsatisfying work (e.g. bureaucratic paperwork, interruptions for unimportant issues, unchallenging problems, etc). Conversely, if I am actually able to code and develop an application that is semi-interesting, I could easily go past 40 hours a week and not feel any burnout because it is fulfilling and/or enjoyable. I could also stay at 40 or a little below.

The key consideration is (perceived) fulfillment. Time spent is involved in determining this, but isn't the only variable - importance of work, enjoyment/satisfaction, sense of accomplishment, etc.

[normloman]

You're right. It's not just a matter of hours worked. Fufillment plays into it too. But even a job you love can burn out if you do it for too long. What's more, most of you consider programming a fulfilling career. So if you're burning out, it's probably due to your long hours. And we know programmers work long hours. So do the math.