But that's usually only if you don't factor in resulting burnout. Experienced developers recognize this and is why they're more reluctant to work for hour-demanders.
What circumstances?
Also, programming trance can last at most a week and you can't do it more often than once or twice a year. There are physical limits to what your brain can sustain.
http://devopsangle.com/2012/04/18/what-research-says-about-w...
Problem is, it's not a "superpower" that can be switched on at-will; it's a state of concentration that requires not only work ethic but a real, intense interest in the subject and a lack of competing thoughts and obligations.
...And then I'm so exhausted that I'm useless for a week afterward. So it's not really all that useful unless I'm up against an absolutely immobile deadline.
You can try to optimize both, but the problem with labor is that productivity per hour is not a constant. Even manual labor may see diminishing returns when working lots of overtime. In fact with manual labor the diminishing returns are often fairly easy to measure. With programming, it's much harder to predict.