Clickbait titles aside, how you use your signals is important. Not just for measuring code coverage.
When you say you want quality software, what are you really asking for, and how can you get it?
Just what is readability anyway?
That’s pretty clever, so fix it.
Naming is important. Even if it’s applesauce
Some kinds of tests you just don’t want to write
There is a difference between testing before and after coding
Tests are like cleaning the lint filter on your dryer
Is it someone’s fault, the system’s fault, or a balance of both?
The purpose of testing is to increase confidence for stakeholders through evidence.