> in codebases where the authors seemed opposed to writing good comments, tests are extremely useful in documenting expected behavior in edge cases
In other words, tests are useful in teams with awful engineering culture. I tend to agree, in my experience they are almost synonymous.
If you treat engineering culture as weather (i.e. something you have no control over), then tests are a good tool to address your problems.
> you're creating a permanent record where you can be held accountable if you miss something
Bureaucracy is another word for it. You know who excels at it? Government. And you know what government is really bad at? Running business and innovating.
In other words, tests are useful in teams with awful engineering culture. I tend to agree, in my experience they are almost synonymous.
If you treat engineering culture as weather (i.e. something you have no control over), then tests are a good tool to address your problems.
> you're creating a permanent record where you can be held accountable if you miss something
Bureaucracy is another word for it. You know who excels at it? Government. And you know what government is really bad at? Running business and innovating.