Maximizing Efficiency By Taking Breaks
On every project there comes a moment where an obstacle keeps you from progressing. Either you can’t figure out a design element in your gameplay, you are uninspired for a particular level design, or there is a bug you simply cannot track down. If the clock is ticking, or you are highly motivated, your inclination might be to grind the problem until a solution presents itself. While there are many situations where this is the only option (like a deadline that is hours away), if you have the ability, you should take a break. Something I’ve learned over the years is that taking a break is the best way to make progress when you’re stumped.
Everyone needs to take breaks. There are dozens of studies that prove that efficiency improves dramatically when people take regular breaks. The question, then, is when is the best time to take a break?
Many people like to use breaks as a reward. “I just need to fix this collision detection bug before I can take a break.” In my experience, this is exactly the wrong approach.
You operate most effectively when your confidence is high and you have lots of energy and mental acuity. If you don’t take a break until after you overcome your obstacle, that last grind will have neither. If you are desperate, you will try lots of really bad solutions to your problem. Rarely will any of these work, and if you had a little more confidence or clarity, you probably wouldn’t have wasted your time on those solutions in the first place.
When you hit an obstacle that you cannot figure out, that’s precisely when you should take your break. Whether it is a trip to the restroom, lunch or just a quick walk outside. Your subconscious will kick in and use your idle brain cycles to work on your solution from new angles. Your conscious, however, will be engaged in what you’re currently doing, which will give it an opportunity to rest and recuperate.
You’ll return to your issue with a sharper mind and you will very quickly come up with a solution that just works. Many times it will be so obvious that you want to kick yourself. You’ll wonder how much time you could have saved if you had only taken your break a little sooner.
For maximum efficiency, you have to consider your break times as little release valves that let you step away from a difficult problem and return to it with greater focus and efficiency. Sometimes you just need a little break to have a breakthrough.




Michael J Williams
So true! Though I think it matters what exactly you do on your break. I’ve found that, for me, going for a walk (or just pacing about) works best; I don’t think I’ve ever had a breakthrough after sitting in front of the TV.
January 2nd, 2009 at 4:47 pmurbansquall
A very important point, Michael. I totally agree.
January 4th, 2009 at 12:35 pmM0RPh1n3
I think I butt my head against that wall often. Anytime I spend more than 10-15 minutes on a bug I’ve run across I drop out and go say hi to the wife or a friend for a bit. Almost 100% of the time I fix the issue within minutes of returning.
I agree with Michael. When I was younger I used to stop and play a game or something. Taking a break had never helped me until I started actually leaving the room and doing something completely different.
January 10th, 2009 at 2:39 amMichael
My introduction to programming coincided with the 2 years of my life that I considered myself to be a smoker. I absolutely loved every cigarette… but that’s another story
Every hour or two, as you do, I would step out onto my balcony for a deep breath of smoke-infused serenity and I often found that I returned having solved the problem at hand.
I put this down to actually trying to solve the problem without the distraction of the keyboard. We often try a trial-and-error approach to fixing things… when you’re forced to step away, the real problem presents itself and the path to the solution becomes much clearer.
Whilst I don’t endorse smoking (or do I?!?!) I do miss those nicotine-inspired moments of clarity.
January 28th, 2009 at 6:06 pm