I don't think avoiding it is the answer... (Score 1)

I know that this runs against most other people's comments, but I've found that taking a few days off doesn't do me any good. I end up more stressed because I know I have a deadline to meet. I was struggling with coders block for a long time when I got into a poetry writing class. I was amazed at how much of the professors sudgestions applied to both poetry and coding. Here are some that work for me. 1. Just write anything!: If I don't know what to write I'll just start writing stuff that I know is wrong. I know I can go back and change it and the natural need for it to be right somehow kicks in and gets me going again. Soon I erase all the "babble" and I'm writing real code again. It's sometimes easier to fix something than it is to create it. 2. If you can, just work up to the problem. In writing poetry you would try by writing a related hi-ku(sp?). In coding, I usually start by writing a little program that might work along side the one I am working on. That gets me thinking about the functions of the code at hand, without pressuring me to work on it. 3. If you havn't started anything yet, just write the stubs. If you hash out the functions and get them to compile with no code in them, you've got something to work with. Also, it's like moving pieces around on a chess board, it gets you to consider your options. Anyway, these are the things that get me through a long day. I hope they work for you. Good luck!!