Two answers for me:

I do my best development work away from the computer. I started this back in school whenever I would run up against a particularly hairy point in the code. Queue up a print job and, when I get a favorable reply from the print daemon (which happened invariably quick since I believed in using the line printer that spew out beautiful beige and green lined continuous pages :), get my printout and go outside with pen/printout and have a smoke. I'd look through the code, marking things up, talking to the world/myself, and puffin' a cig. I found that the time it took to smoke a cigarette was exactly long enough to get me into a different frame of reference and to see the problem in another way.

So when I get back to my desk, with my headphones that block out the rest of the world, and music that reflects my mood (trance for creativity, industrial for debugging), the code just flows through me (don't dock me for the Force reference :) And of course, there's a while loop on this whole answer:

while {!finished}
{
    if (!problem)
    {
        goCode();
    }
    else
    {
        goSmoke();
    }
}
[download]

ALL HAIL BRAK!!!