This is a smart way to think of testing and will discover bugs when your understanding of the code is the most lucid. But it does require some nuance. Unfortun

This is a smart way to think of testing and will discover bugs when your understanding of the code is the most lucid. But it does require some nuance. Unfortunately, some people think writing tests or test harnesses are wasteful because they think of shops that insist on 90%+ coverage and have test suites that are easily 5-10x the size of the application's codebase.... so they decide to forgo them completely. When in reality, the answer is probably something like: you have at least 25% of your codebase that would greatly benefit from testing, even if they're just "smoke tests"