Ok, that sounds wrong. Let me try again: I find that when I'm procrastinating about writing a particular piece of code, it's because there's something nagging at my subconscious telling me "this isn't the right way to solve this particular problems -- go away and think some more".

Once I know what the next step is and know that it's the right next step, I find that I don't procrastinate any more.

Getting in the zone and actually coding solutions up is great (Usually happens late at night when everyone else is asleep for me), but as you say, you need that downtime to think about the next problems.

The biggest barrier to this is the "i'll start right after [X]". Go the the bathroom, chat with someone about an idea, get a cup of coffee, check my mail, comment on a news article, write a blog post about a cool dancing robot, submit a time card, get a long lunch, go to a neighboring cube to get a piece of candy, get a glass of water, check on my finances, etc.

People fill days doing junk like this. Even if interleaved with real work, the lack of focus prevents the coveted "zone". Identify and eliminate everything besides work that you're doing when you should be in a long stretch of work.

A common advice for variants of writer's block is to have some sort of ritual to get you started cranking away. The exact actions are not that important. It could be taking a shower, doing a tea, tidying up your desk, taking some deep breaths, whatever. When you do these things everyday in the same order, your 'muscle memory' eases you into a creative state. I haven't tried this, though.

I'm bad at fighting procrastination. When it gets really bad, I just abuse until I feel the honest urge to get back to work (I mean honest urge as opposed to remorse).

There are some things I found that help when I follow them, although I admit I don't follow them consistently enough:

- Find the time of the day that works best for you. It doesn't need be the same clock time every day. In my case I have screwed sleep patterns (tending to a longer day), so I set it as a delta from my waking time. (I'm considering trying to settle into a 28 hour day, as in http://xkcd.com/320/ , but I'm digressing.)

- Be proactive and aggressive about freeing such time from interruptions.

- Allocate time to do other things you want to do too, including the things you procrastinate in. Doing this helps you not to feel more deprived from (other) fun than from work.

When work time comes and I feel like doing something else, I make myself realise I'm practically missing the working day if I do so. Most times that will get me an honest urge to work. When it doesn't, I just go ahead and do something else all day. I can chain a few days like this, and not everyone can afford this. Eventually I come back refreshed and with no remorse. Other people (and myself, in my late teens/early 20s), would just get into a procrastination/regret spiral instead. YMMV.

And viceversa, if I've spent too much time 'designing' or otherwise thinking about the problem, I unblock by going off and making something I can run. I may eventually throw away that code, but it got me going forward.

So I don't have much of a methodology. Thinking about doing and actually doing are things I do to procrastinate from each other, if you want.

One technique that does help: I keep a stack.txt document, where I write my current tasks (a short phrase each), organized hierarchically (I use indentation because of a Python background; a Lisp native might use sexprs instead). When I stumble into a subtask that I need to do sometime, but which I can get away without for the time being, I 'fake it til I make it', and I enter a reminder of the proper solution in my 'mind stack' as a subtask of the current one. Whenever I think of an unrelated task that I want to do later, I will enter a reminder at the end of the stack. [Edit: OK, so it's a tree, where each path to a leave is a stack of context about what you're doing.]

That avoids two problems that used to get me lost when hacking: getting lost in subtasks and losing context of what I was doing, and trouble deciding what to do next (it's easier to decide with confidence if you can see your options written together).

In the context of an afternoon's work, it might mean you start with a small utility that you know is good but might not have any immediate value, or some optimization tweak that's been itching you for awhile. That'll get you immersed into the project and excited about further possibilities, so tackling drudge-work won't seem so bad.

That idea also applies more generally, and is often the idea alluded to when you hear people around here talk about banging out a 'Version 1' as fast as possible.

One, think of what you have to do and find the smallest possible task that's still interesting (e.g read the first paragraph of a book, write the cornerstone function of your program and leave the menus for later) and start with that. Chances are that, as you go along, your interest in the subject will build and you'll end up working for hours.

Two, find a way to make that disgusting job fun. Maybe you can write the most important part of your program in your favourite language and the GUI in the one you've wanted to learn for years but haven't had the time, so you are still using your time wisely in spite of writing a GUI.

It's all about tricking yourself.

So whenever you feel like procrastinating, tough it out, clench your teeth, and just start.

note: <-- just a joke, obviously

My clock gives me one hour, when I find that I am procrastinating, I turn the clock and promise myself not to do much else other than work till the clock is running. works every time. But their is some sort of ritualistic behaviour involved. you have to respect and even fear the sand clock for this to work.

I use a pair of Audio-Technica ATH-ANC7 QuietPoint Active Noise-Cancelling Headphones - they have been a god sent for me.

It's simple, if you're not excited enough to automatically "get in the zone," then it's not worth struggling or trying to get in the zone... do what you love, the rest comes naturally

Yes, dangerous advice. But it's the truth.

First, is that when I take that approach I invariably wind up with two dozen half-started projects and do very little to build up long-term skills. There are so many things that I love, if I stopped every time I hit a dip to try something else, I'd never finish anything. Plus, one of the things I love is the sense of satisfaction of completing something and doing it well-- especially if I have made a commitment to someone. If rewards are too far off to affect me emotionally, and only my rational brain knows they will be worth it in the end, then I need other way to help stay focused.

The second issue is that there are good things in life that you can't do 'in the zone.' Meeting new people, for example, doesn't require the meditative attention that hacking does. So finding yourself outside the zone for significant periods of time is rather common and not a bad thing. One needs some way to keep that from derailing productivity, however.

In ideas.txt, what I'm focused on now is always at the top.

Everything you see in that screenshot is done and released. I work mostly in 35-minute train rides. Some weeks about 5 hours is all I get to spend. Am I getting more done than you? Be embarrassed and crank. Better yet, post what you're going to do and do it.

More about public embarrassment as motivation can be found here:

http://www.paulgraham.com/die.html

Or, just promise yourself that you'll do just 5 minutes on it and usually once you get going you don't want to stop.

To stay in the zone, /away on AIM/Gtalk, check email once per hour (thanks, The 4 Hour Work Week), phone on vibrate or off. Making sure processes are handled as a queue and not a stack so as to avoid the mania (stress++) of putting out 1000 small fires.

No re-prioritizing anything if someone manages to get through the screens above.

Most of all, as mentioned in another thread earlier, remembering that this is a lifestyle; "ok I'll just binge now and start doing x,y,z when I've [launched, fixed those bugs, implemented the next feature, gotten funding, ... ]" is a way to burn out and ignore the value of and need for finesse and balance in all things.