views:

145

answers:

7

Waiting for the end of compile is extremely boring.

So I used to do Stackoverflow and so on..

What do you usually do ?

and sorry about my poor English

A: 

Make a community wiki.

Dustin Laine
Make your statement a comment not an answer.
TrickyM66
It's technically a valid answer
int3
A: 

I usually go over to someone else's computer and help them.

+9  A: 

From xkcd:

alt text

David Johnstone
ah, i waitet for that answer :)
knittl
+2  A: 

Look for a job that only uses dynamic languages with no separate compile step.

bignose
+1  A: 

For complex systems which take 20+ minutes, even when distributed onto 10+ compile servers, I do as much work as I can without requiring a long compile. Then, when about to go home for the day, off to lunch, or to a meeting, make the changes which require long compilation and then do a build all.

Of other systems, I can't recall any taking more than a minute (unless I'm using Microsoft tools), so there's mere seconds to reflect on what the next most important thing to do is.

wallyk
A: 

I don't usually need to wait longer than a minute max. (D compiles really fast) and the c# stuff I do usually isn't big enough to take that much time. Most the really big things I work on are in php and don't need to be compiled at all.

Doing something other than waiting seems to be counterproductive in pretty much everything I do. although I do get annoyed if I find a type after instinctively building a project after saving the current file and then noticing a type before its finished.

Kris
+2  A: 

Browse and answer questions on stackoverflow.com

jpartogi