[eelinow]

I agree with you as well. Zone time is usually a 3-4 hour a day deal. Some people are honest about it, others aren't. There are short periods of time in which one can code at their top level for a long period of time but these are infrequent. In general I'd say that one can get a good 4 hours of solid work in on a given day. Once going beyond that time frame, especially on a regular basis just increases the chance of introducing errors into a system. The other time would be better spent thinking about the problems faced by the design and or relaxing to allow for ideas to form and work themselves to clarity.

When I used to work outside of my home this meant playing table tennis or fußball as a clearing ones mind method. Or going for a walk outside of the workplace.

The gung-ho brute forcing of a coding method is a dangerous path to traverse. I'm more for the cyclical clear ones mind, allow the design/ideas/concepts to brew. Commit to code the portion at hand then cool down and repeat the cycle.

Honestly, my best clarity comes at 2am, the shower and/or commutes >20 minutes.

Eric codedevl.blogspot.com