Jan 29, 2010
Insist on Automatic Tests
At some point your team is going to be gone. Not all at once (well, maybe, but in that case you won’t care), but over time turnover will completely replace your team.
If you are the manager, and you outlast the team, you’re going to pay for low quality code when you try to bring in new people and they end up breaking everything becuase there’s no tests to check their bug fixes and/or enhancements.
If you are a surviving member of the team, you’re going to pay with huge headaches because you’ve got to fix code where you have no idea what might be broken as a result.
Change is scary when you don’t have automatic tests. Just suck it up and write the tests!
Like this post? Get updates from my feed.
Related posts:
- One Simple Step for Avoiding Shallow Reviews It's your job as a reviewer to find as many...
- Who Else Wants Better Short Term Memory? In “Talent is Overrated”, Geoff Colvin at one point...
- Makefiles are Software Too This post was inspired by recent experience with some...
- Yet Another Python Enum Module I didn’t like the existing enum recipes, so I...
- 9 “Must-Have” Tools for Software Teams The items below are useful systems based on my...