It's not always clear that faster machines really produce net productivity gains, unless the employee's time is already saturated with work. The net gains may manifest themselves into lower working hours, but the company can't just then start paying employees for 7.5 hours instead of 8 (although it can let go of 5% of the workforce to the same effect).
But employees can get more done in their 7.5 hours then they could in 8.
Rather, those 7.5 hours are less interrupted by waits, lag, pauses and compiles. Switching from IDE to reference is more seamless, and so the preservation of flow is much more likely.
Comments
It's not always clear that faster machines really produce net productivity gains, unless the employee's time is already saturated with work. The net gains may manifest themselves into lower working hours, but the company can't just then start paying employees for 7.5 hours instead of 8 (although it can let go of 5% of the workforce to the same effect).
But employees can get more done in their 7.5 hours then they could in 8.
Rather, those 7.5 hours are less interrupted by waits, lag, pauses and compiles. Switching from IDE to reference is more seamless, and so the preservation of flow is much more likely.