[jamedjo]

Is it a code problem or a productivity problem?

Code productivity: Using issue tracking like FogBugz or Github really helps you make sure you work on the important bits first to get a minimum viable product.

I try to think 'Lean Startup' on my projects. Only create the features you really need. Get the bare minimum thing working properly and get feedback/testing from someone who would actually use your product/service. Iterate. Be agile.

More generally: The basic productivity techniques can be a distracting read http://www.43folders.com/howto.

Breaking things down to much can create overhead. I've been trying to improve the way I stay on task. Not just working on the project, but working on the most critical parts without getting distracted. Its too easy go on a tangent, and research something which wasn't critical.

I'm currently refining a method I call ReasearchLock: keeping track of the current task so I don't deviate from it. Things which appear critical often turned out not to be if I tried to get by without them and just left them for later.

I outlined my original idea in a note: http://njoin.co.uk/grains/5107d5516decf91f10000002 but have refined it since.