Coding : Pause vs HyperProductiveWork™

Now I tend to adopt only two modes when coding :

• pause
• or work, but not a "regular, nice work". When I code I try to be as fast and productive as possible. Which means the next thing I have to code is 1) a top-priority and 2) already crystal clear about how to code it.

I try to avoid any intermediate state. If I code too slowly for too long time, it means the spec wasn't clear enough, or maybe I'm diving into a side-feature, nice-to-have stuffs, or too complex implementation.

At that point it's time for a break.

Moreover almost all solutions to complex problems are solved during pause time (sleep, coffee, reading, whatever).

Any thought ?