> Write tests for code that could actually be wrong, or where you need to prove to yourself or others that the invariant is maintained. Yes, what you need to d

> Write tests for code that could actually be wrong, or where you need to prove to yourself or others that the invariant is maintained. Yes, what you need to do in the end, is to use your judgement. But you will get a surprising amount of pushback against this obvious common sense solution. From management who thinks it's too risky, and from developers who have chosen a technical career just because they want to rely on their intelligence, and black and white thinking, and now you're asking them to make trade offs and decisions which is management territory. The way out in my opinion is to make technical leaders that have actual authority, down to the details.