Re:Avoiding "the stupid hour"
by tankbot on Saturday November 24, 2012 @11:14PM
(#4827248)
This is a very interesting philosophy I would like to hear more about. I suspect it is different for coding? It seems like tracking down all of the connected logic bits would be difficult after writing deliriously.
[ Parent
| on HN ]
Re:Avoiding "the stupid hour"
by seanmcdirmid on Saturday November 24, 2012 @11:57PM
(#4827315)
Coding is much the same way as writing to me; they are both forms of thought development and refinement. But then I write research code, not production code, so life is a bit different for me (prototypes vs. products). If you are applying and checking in a bug fix, you don't want to do that in your off hours. If you are building a compiler/interpreter/editor for a new language from scratch to explore some design ideas, then off hours are useful in pushing things along since there are lots of unknowns that require time to mull over. Also, you get something to sleep on.