I'm not a software developer so hopefully this question isn't totally ignorant, but if you're doing tens of edit/compile cycles a day and each compile cycle takes 10 minutes, then it seems like a good use of that time would be using it to work on shortening the compile cycle.

You're talking about an hour of unproductive work a day--an hour I can see you not being able to fill day-after-day. Channeling that time into streamlining your compile process seems like it would pay of handsomely, and more if you're not the only developer with this issue.

In the case that the compile time is limited by some sort of hardware restriction you don't have the power to improve on your own (e.g. scripts and other type of automation can't solve the compile time problem for you), then I'd gather the data on "wasted" time and take it along with an accounting of what you need to the person who has the authority to help you and make your case.

Decompress while it's compiling. Your right brain will continue to work on coding. Don't do something else productive. Watch some semi-lame movie that's barely enough to keep your interest. Read your rss feeder desultorily. Capture ideas and todo items that pop into your head during this time. A 10 minute break is nothing. Work out a little, stretch, walk around, whatever.

Doing minor organization like you mentioned is not a bad idea either.

Very good question! I would like to add a suggestion that can easily be combined with all other sugegstion already given: optimize your computer! When I look at my computer while compiling, most of the time the CPU is not working as hard as you'd expect. Most of the time it's just waiting on the harddrive. Optimizing the hard drive can be done by creating several partitions: one for your source code, one for the object code, and one for all other things. This keeps the harddrive from becoming fragmented quickly. You'd be amazed by the performance gains. Another option is to replace the hard drive by a solid state drive.

Also, what kind of versioning system do you use? I have learned that subversion, and especially the tortoise tools cause enormous cpu and disk usage.

Something that I do at times is to work on two things: Work on project A until I reach the point where I need to compile/ask someone a question/something else that blocks my progress thread. So, I kick off that thread, and switch to project B and do the same thing. Typically the blocked thread will have cleared by the time I block on project B. It doesn't do away with the task-switching overhead, but at least my segments of time are decided by project realities, rather than some "optimum" length of time.

But then, I'm also looking at the pomodoro technique, so all of what I said might be completely invalidated as time passes.

I find that doing simple, easily interruptible, and absolutely non-work-related things, usually online (skimming the news, looking for interesting stackoverflow questions but not actually reading them in detail, social sites), makes returning to the original task much easier than if I try to work on another project or even a different part of the same project in the meantime.

I know it seems like a waste of time, but I haven't found anything better. Trying to spend that time on work so I'd feel like I wasn't wasting it would just make me less productive overall.

Of course, getting up to stretch a bit, rest your eyes and have a drink of water is great too, if you're not doing it every fifteen minutes.

(Note: this answer applies if your breaks are on the 10-20 minute timescale - if they're longer, doing something more involved is probably a good idea, see other answers.)

Push-ups :) The longer it compiles, more push-ups you do. You then get motivated to code it so that it compiles faster. If you can't shorten compile time, you become stronger physically.

This is an older question, but I thought I'd give my 2 cents:

1. Write some unit tests to perform e.g. in a spreadsheet, write a list of things you want to test for this software
2. Lookup / Answer related questions on Stack Exchange
3. Set appointments in your calendar for other things you are thinking about - that way you can clear your head and focus on the task at hand

Meditate.

Your biggest risk is losing focus or flow if you start swordfighting. Meditation not only helps you maintain focus, but it helps defragment other things floating around in your head.

It's not hard. Sit in a relaxed position. Breathe in. Hold your breath. Breathe out. You'll have a bunch of random thoughts come and go. You can jot those down on let them go past and ignore them.

Another alternative is doing some design related to work. Make flowcharts or wireframes on paper.

Do planning: think about what you are going to do after the compilation finishes.

• Jot down some plans for your next steps.

Pen-and-paper is best for sketching short-hand ideas. I also write in a Campfire chatroom or on 750words.com. Putting things into words helps to clarify them.

• Update your task on the issue tracker: progress, clarify description, chosen approach.

• Take a walk around and let your brain mull over what you're working on in peace.

Don't check email or news or social media, don't start work on something else. They start you thinking about other things, leading to a major context switch to get back into the task after the compile finishes, and they can turn into a lot more time than just a compile.

I am a newbie programmer and have had similar situation compiling modules for GNOME Desktop project. These things worked for me:

1. Setting up a audible notification for when the compilation finishes but being within earshot to notice this.

2. Moving away from desk because I would know when compilation has finished and doing something physical such as watering plants or doing the dishes.

3. When I was in a short compilation time frame, I would turn away from the computer and write a note to self on what I felt about work so far or where I am stuck. Just writing down my current thoughts on paper gave much clarity on what I wanted to next.

Hope this helps!

Here's something I just came up with myself, but it is highly dependent on the way your dev team operates:

1. If your team practices doing code reviews independently, check for any pending code reviews, and review them. You don't have to finish the review entirely and stepping away from that code and going back to it intermittently might actually help you spot new things you never noticed before.
2. If your team is using any project management software you can check or update the status of your tickets (your PM will be proud)

The first point is very useful but only if your team doesn't do in-person reviews. As mentioned by someone else I've also found TDD to be very useful to keep cycle times down.

I experienced doing parallel jobs which are totally different is the only thing you can do while compiling or more generally while an application is eating a good slice of you CPU.

For example try these, in parallel to slow app:

1. Wokring on another app UI sketch, on paper.
2. Checking facebook
3. Check stackoverflow.com!
4. Thinking on marketing your app, checking new articles on marketing and finding out iOS is much more money market than Android, still!

But don't try reading stories, novels or blogs, because they will attract you and you will come back minutes after END OF COMPILE.

I would highly recommend standing up and taking a break for some sort of (even slightly) physical activity. This can be as simple as taking a walk around your building. This will not only reduce and soften the potentially negative physical side effects of sitting at a desk all day, but it will also allow your brain to decompress. Your subconscious mind will have a chance to sort things out without being impeded by your conscious thought processes. This will keep you from feeling "brain-dead" at the end of the day, and your mental stamina will increase over time.