|
|
|
|
|
|
by cercatrova
2113 days ago
|
|
|
Here is the study I read it from, there might be others. In my experience, yes, it doesn't work for managers, only those who are individual contributors doing programming full time. I doubt however that even the senior managers are coding the entire time for 4 to 6 hours, it is difficult to do so every single day. More likely, you perceive them to be doing that much work since they are present during that time, which is the same reaction I get as well; colleagues and bosses speak of how much work I get done compared to others, yet they don't realize I work a lot fewer hours. It's all about efficiency. https://www.inc.com/melanie-curtin/in-an-8-hour-day-the-aver... |
|
|
> However, this eight-hour movement didn't become standard until nearly a century later, when, in 1914, Ford Motor Company astonished everyone by cutting daily hours down to eight while simultaneously doubling wages. The result? Increased productivity.
What happened was the shift from craftsmen at a workbench to a deskilled assembly line had significant turnover. The cost of training and retention was high enough that Ford instituted the lower working hours and higher wages.
From one of Ford's biographers: “So great was labor’s distaste for the new machine system that toward the close of 1913 every time the company wanted to add 100 men to its factory personnel, it was necessary to hire 963.”
You see this in shipyards during the war war 2 years where once the initial pool of workers is burned out, you need to raise wages to bring in more workers.