Don't be an avoider

In my earlier interview with Frank Westphal I noted that Contemplative Programmers, when stuck on a problem, defer it and direct their attention to another needy task. I realize that this practice, even more so when given as an advice, can be misunderstood, even abused as an excuse for unhealthy conduct. To be clear, Contemplative Programming doesn't license Ersatzhandlungen (substitute acts). We want and we want you to stay on track. There are times when this is not easy at all.

Some problems mount up to terrifying heights. Then there are problems who look innocuous, whereas they are anything but. They inspire fear -- the fear of failing. In order to avoid such a problem all kinds of other "really urgent" things spring to mind. Most likely they aren't very urgent at all -- they just lead to Ersatzhandlungen. They make you appear busy while not doing what needs to be done. One of the core values of Extreme Programming is courage and that's the apt cure from a Contemplative Programming point of view, too. Still, we tend to allot a different dose.

Avoiding problems that need to be tackled is bad, that much we have established. But clinging helplessly and undproductively to a problem is only slightly less bad. Yes, by all means muster the courage to attack the really important problems -- but be brave enough to let them go for a while if you don't make any progress. The point here is to tackle a problem on your terms, when you are in the best position to actually handle and solve it.

So, don't avoid problems, you may defer them, though.