tags:

views:

477

answers:

19

Sometimes it takes about a minute or two to fully compile an application. Believe me, that's a long time. You've obviously just looked at the code and just waiting to see some results, etc.

I was wondering, what do you do during that 1 to 2+ minutes?

+1  A: 
  • bathroom break
  • get a drink
  • nothing
  • surf SO some more
  • wonder when "a minute or two" became a long time :D
warren
+9  A: 

Post on StackOverflow.

Currently waiting for a compile :)

JaredPar
[syntax error: Diddo: undefined variable (did you mean "Ditto")?] ;)
Jimmy
+4  A: 

swordfight on officechairs (sorry, no SO thread is allowed to not have an xkcd reference)

Jimmy
http://xkcd.com/303/
aib
+2  A: 

Get my ass out of the chair, maybe even stretch my legs a bit and fill up my mug (office next door to break room).

Or depending on the build I may watch output

curtisk
+2  A: 

Spend the two minutes coding in Python! (no compile needed...)

Ned Batchelder
no local compile needed... lets pass it on to the user :(
baash05
Depends if your boss is a stickler and makes you use py2exe :(
John T
A: 

I write in C# 3.0 {cheerfully} and VB9 {regretfully}. One advantage they both share is that it takes almost no time to compile and run. 10 seconds mayhap.

David Leon
A: 

I don't wait for compilation too often, I use ReSharper.

Ilya Ryzhenkov
+2  A: 

I remember my builds used to take 30 minutes on a fast box (and you couldn't optimize it much, the damn link was 20 of that.

I took apart a hard drive and rebuilt it as a little guy (read/write head) surfing on the disks. Lots of the other pieces were scenery.

My boss told me later that he came in to lay me off one day (Took me a while to get the hang of C) and asked about it and I told him I made it during builds. He said it saved my job--kinda creative I guess. (I'm sure he didn't WANT to get rid of me, and later said he was really glad he hadn't.)

Bill K
That is kind of messed up. I don't really see the connection with some office trinket you put together during down time and not getting laid off.
Simucal
Just that he figured I was a little more creative than he'd thought. He was right too--made a bunch of money for that company thinking and working "outside the box". Ugh, how lame that sounds, but really--it worked out well, and he was right. The guy was an amazing manager overall.
Bill K
A: 

For me, an incremental build usually takes about 5 minutes so I will read some RSS feeds or post on SO. For full builds, it will take between 1 and 2.5 hours (depending on how many cores I use for the build), so I'll go play pool, play foosball, go out to lunch... sometimes all of the above. And it still won't be done when I get back. I try to always run the full builds overnight, but sometimes something happens (like the build is broken) and it totally kills my productivity for a day.

rmeador
A: 

I generally stare blankly at the terminal. Sometimes I also twiddle my thumbs, or drum my fingers on my palmrest.

Adam Jaskiewicz
A: 

Take another sip of coffee and prepare for the next step (deploying, testing, whatever).

-R

Huntrods
+7  A: 
JWD
ugh. Hotlinking---
gnud
+3  A: 

Praying...

serg
A: 

it depends on the need. Most times I write notes. I use an exercise ball for an office chair, if I'm up to date on my notes, I do situps.

baash05
A: 

I code in ruby, so I never have to wait for a compile.

While I'm waiting for unit tests however... I make a coffee, drink it, go to the bathroom, read codinghorror and stackoverflow, and yawn a lot :-)

Orion Edwards
A: 

I blink a few times. Delphi :)

utku_karatas
Why am I imagining someone blinking really slowly for five minutes?
Pete Kirkham
That's probably because you don't know Delphi compiles in miliseconds to a few seconds at most. :)
utku_karatas
A: 

SO, failblog, and dailywtf are all on the rotation

Matt Briggs
A: 

Since it took 3 minutes to compile, I would race it trying to finish a Rubik's Cube. (This is a very old story. In fact, s/compile/assemble !)

gbarry