News for hackers. Stuff that matters.
Re:Poll: how many productive hours do you have in a day? by sitkack on Monday April 28, 2014 @12:56PM (#7661190)
I find the best way to accomplish this is a more scientific task breakdown. When a road block is encountered that would normally disrupt flow I stand back and analyze the subproblem with new desired outcomes.

The most time consuming and frustrating problems usually have some element of psychological aversion. Like involving a language, tool or subject matter that I either dislike or don't feel confident in solving. Break down the reasons for the aversion and jump right in!

Just last week I had an issue that I realized could be solved with some judicious GDB. I spent 3 hours just learning the tool, solved my problem and checked off a mental handicap.

Don't require "successful outcomes" all the time, slowly and methodically enjoy the journey and keep on eye on forward progress but don't demand it.

Re:Poll: how many productive hours do you have in a day? by Swizec on Monday April 28, 2014 @02:43PM (#7662026)
> Don't require "successful outcomes" all the time, slowly and methodically enjoy the journey and keep on eye on forward progress but don't demand it.

Which is exactly where most of these "I can code all day, I can code all day"[1] programmers fail. As soon as an obstacle comes, they crash and burn because they are too used to riding a wave of endorphins.

[1] reference to FPSDoug, in case anyone remembers him.