Re:Why You Shouldn't Interrupt a Programmer
by yeukhon on Monday October 28, 2013 @10:26AM
(#6627101)
True and a quiet day might be enough as an pill.
Or at least sitting at home can help for some people.
Re:Why You Shouldn't Interrupt a Programmer
by dasil003 on Monday October 28, 2013 @12:23PM
(#6627846)
Not sure why someone downvoted you. While it's true that not all work is pleasant and sometimes we have to force ourselves to get things done, I think it's equally true that for solving difficult problems reflection is necessary. Especially as I get older and more experienced, I feel like my brain has more fodder for solutions but it takes more time to tumble around and fall into place. A lot of things besides actually sitting down and coding can help: getting 8-9 hours of sleep, talking over the problem with someone (even non-technical), getting some exercise, mind-mapping / wireframing, staring into space for hours at a time, etc.
Writing that crappy code that feels like pulling barbed wire through your brain forces you to think about the problem. To look at the corner cases, to really figure out a solution.
The breakthrough in a few days is just a cleaner solution you were able to come to after a deep understanding of the problem.