Why Test-Driven Development is Necessary?
TDD at Its Best
Test-Driven Development (TDD) is one of the most debated topics of software engineering. Some people think it’s indispensable, and on the other hand, some people think it’s nonsense.
My opinions are not that hard on TDD towards either of the sides. However, I have good reasons to think it’s a great practice to design better software.
I’ve been developing software for 15+ years and managing development teams for almost 8 years. Here’s what I learned about TDD and why I think it’s a great practice.
Why Don’t We Use TDD?
First of all, let’s talk about the opposite side. Why don’t people use TDD? I see three reasons in general. But let me tell you something, it all goes down to being “hard.” So the main reason why people don’t use TDD is that they think it’s hard. Hint, it’s not. But first things first.
It’s Hard to Think
For us developers, writing code is sometimes easier than thinking about it. That’s why when we have an app idea, we generally start coding it without planning ahead.
We call it prototyping, and it’s a good practice as well. Still, the problem is what we do after building a prototype: We make the app upon that prototype, rather than…
