[somebear]

This is one of my biggest problems. When compilation, image creation, or device flashing takes longer than ~1 minute, then I will switch to the browser and get lost. 15-30 minutes later I will discover that my build, flash file, whatever was done, and will resume work (and feel really bad about it).

[yummyfajitas]

Instead of browsing, I do situps, pushups, etc. I get back to work the second my simulation finishes.

Well, sometimes I do that. It is effective when I do it.

[troutwine]

Interesting. I try to keep a newspaper or periodical handy, something offline and inert. While my project compiles, I read a few hundred words and do not get so engrossed I lose my original train of thought.

[somebear]

I think my colleagues would start to look even more funnily at me than the already do if I started doing this. Especially since we work in an open office environment. If I had an office I would definitely consider.

For now I think I will try and heed troutwine's advice: http://news.ycombinator.com/item?id=1379082

[jessor]

I'm still working on this, too. Read the classic NADD description: http://randsinrepose.com/archives/2003/07/10/nadd.html if you don't know it yet ;)

[levesque]

If you use Visual Studio, you can setup a sound to play when the build is finished.

[ekanes]

Setting a timer (even for just 3 minutes) works well for this problem.