[mtrimpe]

I think in this case it's actually relevant to mention age, because I'm more and more inclined to believe that while 60+ hours can be a good thing to do in your twenties, especially if your digital life is your social life, but that it rarely ever is a smart thing to do after you're thirty.

Young coders don't have that much experience yet and will often have to rely on their brawn rather than their wit which could perhaps make the 60+ hours thing a solid strategic choice.

As I've grown older I've found that I can deliver much more value with much less effort by being well rested and taking a step back to see what's actually the important thing to do.

Whether I'm doing so because I've become wiser or because I've become less effective in those long hours is a different question altogether of course.