Member-only story
The one thing every junior developer needs to know about TDD
Imagine spending a full week developing your software, your best piece of art. One day after the release, many people are now experiencing bugs and crashes. Strange, but you’re full of energy and willingness to do, so you immediately start to fix those problems. Nonetheless, you soon realize that for one simple and innocent bug you are now forced to rewrite 80% of your code.
And the cycles continues, the initial one week of work is now doubled, and then a month, six months, a full year. Your software is now unmaintainable. You have now 2 choices:
1) Rewrite the entire source code
2) Abandon the project
Pretty drastic huh? But that’s how most inexperienced programmers write software, quick and dirty. And since the world has more junior than senior developers, you’ll often find this pattern even in some big companies.
This image is essentially explaining what I’ve just told you. It’s called the software development curve, and it shows how development speed is correlated to time.
