[kscaldef]

I think it's more interesting to look at what the crossing point is where it becomes useful to multitask.

Surely, when on hold with some company listening to "your call is valuable to us; please do not hang up; the expected wait time is 45 minutes" he wouldn't advise to just be on the phone.

When I need to run a 5 minute test suite before checking in some code, should I go read my email while I wait? What if it's 30 seconds instead?

Where is that point where switching to another task is the right thing to do?

[biggitybones]

This is a great point, and something I struggle with. Although, I think it combines the problem of focus as well.

While waiting for my project to compile and start, I switch to my browser, get lost in HN or e-mail and 5 or 10 min later forget what I was doing in the first place. When this happens several times a day, it becomes a real problem.

[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.

[Periodic]

There's definitely a place where it gets too extreme. I've caught myself going to check IMs and emails while a page loads in the browser. I pause in my writing at the end of a sentence and I flick my gaze over to check for new mail.

I think the point at which you can switch is when you can honestly expect to give the thing you are switching to your full attention until it is complete. So sure, go answer a few emails during a compile, but only check for the compile to be done in between emails.

[kscaldef]

Absolutely... I think something like Growl is useful here to let you know "your compile is done" or "your tests are finished running".

[Periodic]

If it's just reading HN I could see this, but I don't think it's a good solution. The very problem we have is too many notifications. Whether they are mail or test suites, they interrupt you and take your focus, even briefly, away from what you're currently doing.

[kscaldef]

I turn off notifications on mail, Skype chat, IRC, etc. If it's not more important than the other things I might be doing, it doesn't get to interrupt me.

[beagle3]

Add a command to make a sound and/or push the build window / ide forward at the end of the compile. It really is as simple as that if you want it.