(When I’m teaching and coaching, I have a number of themes that I discuss and that will show up somewhere in everything I do. Here’s the money theme, which I usually bring up at the earliest opportunity.)
Look, kids, we’re in this for the money.
Somehow you got the idea that TDD, pairing, micro-stepping, and refactoring are not about increasing your productivity.
It could be the misguided craftsmanship movement, who give you the excuse to say “we don’t have time for art.” Or maybe you heard it from nay-sayers who are against these notions from the get-go. Maybe you read stuff from the early days, when we still didn’t understand that internal quality was such a huge determinant of success. Or, worst of all, some of you heard it from people who are in favor of these ideas, but get lost in the thick of things and say stuff they really should know better than to say.
It doesn’t matter how you got the idea, though. The simple fact is it’s entirely untrue.
TDD is in every respect about increasing software development productivity.
It is not about craftsmanship or art or beauty.
It is not about being a good citizen.
It is not about taking some illusory long view instead of the short.
It is not about you being a better person.
It’s not about improving quality.
It’s about money.
Do you want to make more money? Does your company want to make more money?
There are various goals you could aim at to do that. Maybe you need to ship more quality. Maybe you need lots more features. Maybe you need a whole new approach to the problem.
Funny thing, though. No matter what your target is, or even what time-scale it lives in, you will get there faster if you are more productive.
Driving with microtests increases productivity.
The microtests do a number of things to make us faster. See my articles on how TDD works its magic, for the many cases:
- They multiply developer intentions, which provides a powerful “online” memory.
- They demonstrate with a flick of the wrist that a change you just made did not hurt anything.
- Their blinding speed far exceeds any other means of feedback in utility.
- They *force* us to work in small objects with small methods.
In a single phrase? TDD increases productivity because the hard part of programming is thinking, and they make thinking faster.
Pairing increases productivity.
This one’s been demonstrated so many times its not funny. Pairing — at a real pairing station — has the following impacts on productivity:
- Pairs find dumb-assed syntax errors faster than solos.
- Pairs find *shared* language for programmer intention, the most subtle and elusive part of the primary task of programming, which is understanding the code in front of you at a glance.
- Pairs share energy back and forth, which means they can focus on a single task for far longer than solos.
- Pairs are more fun. (Okay, that’s not about productivity. Fine.)
- Pairing is the most efficient mechanism for knowledge transfer.
In a single phrase? Pairing increases productivity because the hard part of programming is thinking, and they make the thinking go faster.
Refactoring increases productivity.
The reason this one’s so hard for the noobs to get is that they haven’t yet understood that the code-to-which-you-are-adding is the single biggest determinant of the speed with which you add. Continuous micro-refactoring provides these benefits to productivity:
- They render the code-base smaller. Smaller = less to grasp. Less to grasp = faster to change.
- They reveal intention, which is the hardest part of code-grasping. Not, “what does this code do”, but “why do we want this code to do this”.
- They continuously improve the overall design, including performance, of the code.
So, you know, in a single phrase? Refactoring increases productivity because the hard part of programming is the thinking, and they make the thinking go faster.
Micro-stepping increases productivity.
We do all of our work, testing, designing, refactoring, really *everything*, guided by one simple question: “what’s the smallest interesting step I can take?” And we do this because micro-steps improve our productivity in these ways:
- They mean smaller scope, meaning fewer independent concepts, meaning easier reasoning.
- They make most bugs emerge in those same small scopes. Time debugging is dramatically reduced.
- They provide readily testable and trackable change. Continuous change is faster than chunky change.
Oh, in a single phrase? Micro-stepping increases productivity because the hard part of programming is the thinking, and micro-stepping makes the thinking go faster.
In The Beginning…
The only time these activities slow you down is in the beginning, when — guess what — you’re still learning their basic mechanics.
Here’s the deep dark secret: working this way is not how you learned to work. How you learned to work was either on-the-job-under-the-gun or buttressed around with perfectly reasonable theories that have no bearing on actual successful practice.
Learning to work this way is hardest for skilled geeks: they have a lot more practice to unlearn. But they’ll also have the biggest productivity gains once they get it.
Step Zero? Set up a decent comfortable pairing rig and invite experts to come and play. They’ll come. Pairing is the beginning, not the end, of this technique.
Learn Your Damned Trade
Too busy to TDD?
Too busy to pair?
Too busy to refactor?
Too busy to micro-test?
I call bullshit. My buddy Erik Meade calls it Stupid Busy, and I think that nails it pretty well. All you’re really saying is that you’re too busy to go faster.