What do you do while building?
-
I'd rather grab a co-workwer and talk to a coffee.
-
I'm working on a project with a long build duration. How do you normally kill time when you return with your coffee and the build is still busy?
I thought that's why The Code Project exists.
-
I'm working on a project with a long build duration. How do you normally kill time when you return with your coffee and the build is still busy?
What kind of software are you writing that takes so long to build? :omg:
-
I'm working on a project with a long build duration. How do you normally kill time when you return with your coffee and the build is still busy?
I used to bring library books for when I was cross-compiling CMS-2 code on a VAX for AN/UYK-20 or 44 Navy computers. That was before the internet. :sigh: Now if I get a chance between builds (rarely) it's XKCD or CP.
SS => Qualified in Submarines "We sleep soundly in our beds because rough men stand ready in the night to visit violence on those who would do us harm". Winston Churchill "Real programmers can write FORTRAN in any language". Unknown
-
bertvan wrote:
How do you normally kill time when you return with your coffee and the build is still busy?
Working out how to speed up the build... Cursing the numpty who didn't distribute their code in files so as to minimise build times... Then I get bored, start surfing t'Internet and come back later to find I've wasted 20 minutes after the build had finished...
Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
Ditto here. I tried multitasking on software related things, but found I would loose too much mental context to make it effective. So I try to do other non-SW tasks, and at worst, keep a very close eye on the build progress so I can immediately switch back when it completes.
patbob
-
I'm working on a project with a long build duration. How do you normally kill time when you return with your coffee and the build is still busy?
Depending on how I'm feeling; 1. Work that doesn't require coding, i.e documentation, writing test cases etc, spec updates, design next piece of system, research better ways of doing something I know is coming up, reading email etc. 2. Hang out on code project or the MS forums and try to either learn something or help someone else.
-
I'm working on a project with a long build duration. How do you normally kill time when you return with your coffee and the build is still busy?
I attempt to destroy someone else's productivity while mine is shot by the crappy computer I was given :)
-
I'd rather grab a co-workwer and talk to a coffee.
I second that: :D
Know way too many languages... master of none!
-
That was an awesome comic link!
Know way too many languages... master of none!
-
I'm working on a project with a long build duration. How do you normally kill time when you return with your coffee and the build is still busy?
Use Freepascal - it compiles and links in one pass - fast as heck. my c++ stuff always takes WAY longer and is more complicated in general (linking wise) than freepascal... I usually watch builds closely for errors. I also try to set things so that not everything is forced to recompile - just new changes. Now for twidling fingers? I read emails and follow up and occasionally end up here like many of the others kicking about.
Know way too many languages... master of none!