Ask HN: What do you do while you're waiting for code to compile?
I often find myself working on something that takes awhile to run. I make a change and then have to wait up to three minutes before I can see the result. It's enough time that I feel silly just staring at the screen, but not long enough to accomplish anything else. So I usually check hn or my email and end up losing 15 or 20 minutes.
There have to be a lot of other people with this problem. What do you do while you're waiting a short time for something to run or compile?
9 comments
[ 2.0 ms ] story [ 30.9 ms ] thread(2) Your build cannot be fast enough. Quite likely you have a machine that was chosen to be crazy cheap (Dell) or crazy beautiful (Mac) but not chosen to be crazy fast. A crazy fast machine with an SSD and the best CPU you can get will improve your productivity enough to pay for itself in 2 months or so if you do the math. Your boss won't believe it, so you might just get one for yourself.
(3) It never hurts to get up and move around
(4) It is not a bad idea to stare at the screen and think. In fact, carefully reading the output of your build should piss you off enough that you do something at (1)
(5) Overall it is dangerous to juggle a large number of balls in the area, but one exception to this is to carve out a single task you can work on while waiting for builds and make switching to and from that task as easy as possible. This task can be anything that makes progress towards your goals, such as sorting the backlog, reading technical documentation, etc.
(6) Set up some kind of chime to ring when your build is done, that will help you get back to it. It's one of those things that people don't seem to do, but it works.
Sometimes I'd read up on technical articles / blog posts related to what I'm working on.
Is it just a really big project, or do there exist languages that compile much slower than others?