This question I guess will remain for long time to come as I see that TDD's adoption is nowhere to be good enough. I shared my thoughts as a post in Hackernoon earlier which caught a zillion eye-balls and heck a lot of readers time.
This post is a re-production of that after a good couple of years now.
I hate TDD (aka Test Driven Development) and think there are a lot of things wrong with it. Only some of them off my mind are below.
In a team practicing TDD for quite a long time:
Teams that has refrained from TDD has the following points by their side:
Let us work together to stop the practice of TDD and bring the old world of chaos and uncertainty.
Hoping you would care to show your love for this written work of mine by.., I am sure, you know what to do.
This post is a re-production of that after a good couple of years now.
I hate TDD (aka Test Driven Development) and think there are a lot of things wrong with it. Only some of them off my mind are below.
 |
| copyright: codonomics |
In a team practicing TDD for quite a long time:
- the after-hours time of spending time in office, fixing bugs that keep propping every now and then is now gone.
- the opportunity for lonely bachelors to compete with family-oriented colleagues by working sleep-less in office is gone.
- the opportunity to intelligent code rather that readable/maintainable code is largely reduced.
- the easy opportunity to look hard-working is gone. I now have to really work hard to look smarter with this TDD, CI and stuff that forces discipline in what I do. I hate it like hell.
- the team’s dependency on me to understand code and its functionality is reduced big-time because the tests act as spec or documentation that talks for itself.
- the easy opportunity cost of amassing a ton of money from my clients for code-refactoring or feature change requests is minimized in a big way.
- the cost of manual testing in terms of time and money is greatly reduced. This practice killed so many QA jobs.
- the easy chance of developer blaming the QA for the bugs is a bygone era.
- evolutionary design and architecture is made possible, making me code everyday. Earlier I used to brag myself as Architect that doesn’t code.
- product go-live anxiousness is nowhere to be seen. Every release used to be a big event earlier.
- and on and on…
Teams that has refrained from TDD has the following points by their side:
- TDD is for the average Joe. My team has no place for him.
- TDD is so damn un-intuitive and really weird.
- TDD is for those junior developers who are not adept in up-front code design.
- My teams has just seasoned developers and domain experts who have been coding this product right from its inception. They are solid hackers. They don’t need TDD.
- TDD hurts our productivity.
- TDD is for those large process oriented enterprises. We don’t have the luxury of time.
- TDD is for those chaotic start-ups that has no processes in place.
- TDD is like buying all the lottery tickets to win the lottery money.
- TDD is no science. We don’t believe in things that not scientific.
- TDD is not magic. Bad test code is worse than bad regular code.
- TDD is so broken. I have not seen 2 TDD specialists solving a problem the same way and using same tool-set.
- and on and on..
Let us work together to stop the practice of TDD and bring the old world of chaos and uncertainty.
 |
| Devil: “Let us work together to stop the practice of TDD and bring the old world of chaos and uncertainty. Game?” |
NOTE: This answer is a parody of the devil inside a developer. You’re expected to have a loud laughter reading this, instead of embracing it. You sure will do good to think about these points instead of dismissing it right away. May “peace to all” be our driving factor. Cheers!
Hoping you would care to show your love for this written work of mine by.., I am sure, you know what to do.