News for hackers. Stuff that matters.
Re:What Programming a Game in 48 Hours Taught Me About Progr... by eitland on Thursday August 29, 2013 @01:03AM (#6294359)
The Pomodoro Technique is a winner for quite a few of us.

Also reading up on perfectionism might be interesting (hint: it often doesn't end with a perfect result but it is always time consuming.) YMMW.

Re:What Programming a Game in 48 Hours Taught Me About Progr... by tehwalrus on Thursday August 29, 2013 @10:38AM (#6296060)
The drawback with pomodoro in Programming is Flow - If it takes even 5 minutes to "ramp up" your brain back into the problem space, then you're throwing away 10 minutes every half hour (and that estimate was highly optimistic) - and you're doing that deliberately.

Much better to eliminate distractions, in my experience (selective site blocker, headphones with white noise or coffee noise or wordless trance, and an IDE that never stalls.)

Re:What Programming a Game in 48 Hours Taught Me About Progr... by Bjartr on Thursday August 29, 2013 @04:35PM (#6298445)
>IDE that never stalls

Why I hate Eclipse

Re:What Programming a Game in 48 Hours Taught Me About Progr... by graeme on Thursday August 29, 2013 @01:13AM (#6294385)
Yeah, I use pomodoro. I'm thinking more of productivity over a 1-3 day period. Maybe I just need better default habits, when I use pomodoro consistently I'm very productive.

I don't think I'm a perfectionist, and agree it is to be avoided.

Re:What Programming a Game in 48 Hours Taught Me About Progr... by jaggederest on Thursday August 29, 2013 @04:32AM (#6294858)
I don't think there is a way to consistently improve your total output without side effects. I worry that this chase for productivity always comes with negative fallout, and people neglect it when pursuing 'more output'. Better output, perhaps? More output? Probably unsustainable.