It took me a long time to get there, but I finally accepted that when I am tired, I shouldn't work. I should rest. The quality of the work that I do when tired is abysmal, and usually requires that it be redone anyway.
For low-latency work more sleep = better. There's no real advantage to pushing long hours. You can sleep and make quick progress when fresh.
For high-latency work that "should" be low-latency (ie you are on the end of a 1 hour pipeline that in an ideal world would be much faster) there can be significant advantages to just pushing more hours. This is a depressingly large % of enterprise work. Basically doing low brain stuff (which is most dev work) but trying to get feedback from the end of a long ci pipeline. I'm not sure this is true "in principle" but my observation is that after you hit baseline competence the people who make the most forward progress in this kind of dysfunctional scenario are the people who just spin the pipeline more and put in more hours.
For writing / proper design / activities where there might be no real safety net and feedback cycle might be years, definitely do that in the morning after good sleep.
