Re:Preindustrial workers worked fewer hours than today's (2009)
by wpietri on Thursday August 22, 2019 @01:03AM
(#20764800)
I think that'd definitely wrong.
Some kinds of coding do benefit from lack of interruption, so that's can be an argument for very focused work. But one way coding is different than, say, factory work or service work, is that our errors accumulate. It takes just seconds to put a bug in, but hours or days to take it out again. So anybody working long enough to get tired will very quickly hit diminishing returns. There's a nice presentation on this from a while back: http://www.lostgarden.com/2008/09/rules-of-productivity-pres...
I also have come to be suspicious of the "hyperfocus for many hours to get large amounts of state into my head" approach to coding. Code I have to be extremely clever to write usually ends up being a giant pain in the ass to maintain. These days I think it's better to use things like unit tests, pair programming, and very frequent releases to get things done.
Some kinds of coding do benefit from lack of interruption, so that's can be an argument for very focused work. But one way coding is different than, say, factory work or service work, is that our errors accumulate. It takes just seconds to put a bug in, but hours or days to take it out again. So anybody working long enough to get tired will very quickly hit diminishing returns. There's a nice presentation on this from a while back: http://www.lostgarden.com/2008/09/rules-of-productivity-pres...
I also have come to be suspicious of the "hyperfocus for many hours to get large amounts of state into my head" approach to coding. Code I have to be extremely clever to write usually ends up being a giant pain in the ass to maintain. These days I think it's better to use things like unit tests, pair programming, and very frequent releases to get things done.