Perhaps in manual labor, but I don't think this applies to white collar work. The limiting factor in output for this line of work seems to be intellectual exhaustion/burnout, not pacing.
Perhaps in manual labor, but I don't think this applies to white collar work. The limiting factor in output for this line of work seems to be intellectual exhaustion/burnout, not pacing.
Personally I assign development to more of a "creative" role than a lot of people tend to. Your productivity can often depend on your inspiration, moreso the more senior/architectural your role is.
I've certainly had moments where I accomplished more at one 3am moment of clarity than an entire week before - and I think most experienced developers can say the same.
My “work hours” in my pay slip say 75.8 for every 2 weeks. I work maybe 50 hours in a busy week. It is irrelevant to my organization. So we are already there in terms of intellectual white collar work.
If the company cared only about getting certain amount of work done in the time they paid for, they would hire an external. And continuing the analogy, it's usually more expensive in the long run to rent a tool even if you use it only a couple of times a month, as well as having to get used to unfamiliar equipment, having no records of how well the rental tool performed earlier.