If you are throwing away your tired-brain code a week later, godspeed. Do what you like. But if you are checking in that code and making other people deal with it, then quality becomes much more important. If you write 1200 lines of code instead of 800, then you have something that has 50% more maintenance cost and 50% more bugs. (And it's probably worse given that you were tired and thinking with a short-term mindset.) So hell yes, it matters to me whether my coworkers are putting long-term value above short-term incentives.
> I'm just tired of everyone being absolutely fascinated by this idea that resting is better than not resting. Isn't that just obvious?
It is not in fact obvious. So many places reward time spent more than quality work. Just today at a meetup we were talking about how to shift people away from damaging and expensive heroics to investing in not creating such big problems that you need work-all-night heroes. The industry is notorious for death marches and work-all-the-time startups. And it's also notorious for buggy, low-productivity, high-tech-debt code bases and giant rewrites caused by years of accumulated short-term thinking.
If it's obvious to you, skip over the articles. Not everything has to be for you.
> I'm just tired of everyone being absolutely fascinated by this idea that resting is better than not resting. Isn't that just obvious?
It is not in fact obvious. So many places reward time spent more than quality work. Just today at a meetup we were talking about how to shift people away from damaging and expensive heroics to investing in not creating such big problems that you need work-all-night heroes. The industry is notorious for death marches and work-all-the-time startups. And it's also notorious for buggy, low-productivity, high-tech-debt code bases and giant rewrites caused by years of accumulated short-term thinking.
If it's obvious to you, skip over the articles. Not everything has to be for you.