Todays topic: “The Jury is in on TDD, there are no more excuses”
- Test driven development is superior
- Test driven design is superior
Patient and meticulous grinding at the base level. Driven by the precise execution of core disciplines, reverberating chants of Red-Green-Refactor down along the aisles of craftsmen.
TDD forces you to taste your own API. The customer comes first. No work is done until the desired task is purposely expressed in jargon meaningful to the client.
You suddenly start to work with a flexible base material. You keep it and yourself flexible by you continuously flexing it.
It is a coding learning experience where the feedback is immediate. Instead of a feedback cycle of hours to weeks, the slap on the wrist is immediate with the guilty misconceptions and the accomplicing mind set still at the scene of the crime.
- Of course it’s a new discipline.
- Of course you will be worse before you get better.
- Of course it takes a different mind set to be the bringer of change rather than hoping to not be awakening the beast.
- Of course you wont find the flow from the get-go.
BUT:
- When you have the assurance of the green light and due confidence in its significance.
- When you play for keeps, knowing that people will have to get by your tests to break it.
- When you don’t have that uneasy feeling of having to go back to recheck something.
- When you know that you check in better code than you checked out.
- And you know it works.
…. then it will start to feel unnatural, and unprofessional, to do anything else.
No comments:
Post a Comment