debingjos writes “Management at my company seems to think that our developers can get extra work done if they work extra long days. However, as one of the devs in question, I don’t agree. When I’ve been coding for eight hours, my pool of concentration is exhausted. Working overtime either fails to produce any extra code, or the quality of the code is very bad. What is the community’s opinion on this? This can be broken out further into several questions: What are the maximum number of hours you can work in a day/week and still be reasonably productive? When you absolutely must work beyond that limit, what steps do you take to minimize degradation of quality? If you’re able to structure your time differently from the typical 9-5 schedule, what method works best for you? Finally, how do you communicate the quality problems to management?”… debingjos writes “Management at my company seems to think that our developers can get extra work done if they work extra long days. However, as one of the devs in question, I don’t agree. When I’ve been coding for eight hours, my pool of concentration is exhausted. Working overtime either fails to produce any extra code, or the quality of the code is very bad. What is the community’s opinion on this? This can be broken out further into several questions: What are the maximum number of hours you can work in a day/week and still be reasonably productive? When you absolutely must work beyond that limit, what steps do you take to minimize degradation of quality? If you’re able to structure your time differently from the typical 9-5 schedule, what method works best for you? Finally, how do you communicate the quality problems to management?”
Read more of this story at Slashdot.
Read more http://rss.slashdot.org/~r/Slashdot/slashdot/~3/5b-8_Ekw9Wk/story01.htm