[mritun]

It can be hard.

The key is to

1) not engage in conversation

2) add mechanical tools that fail the build if coverage isn’t enough!

A lot of times people argue that it’s stupid to have a “target” code coverage. I used to be one such person until I saw what happens when you leave it to people. Most people would still keep quality bar high, but one rotten fish spoils the pond and the tools that mechanically measure quality metrics are very effective in pushing back on bullshit like this.

Oh and whatever you do, don’t engage in debate on this. They /will/ wear you down.

[sshine]

> add mechanical tools that fail the build

I wish this wasn’t so damn effective.

Anecdata says that people who are too stubborn to adapt to other people’s best practices often don’t mind the practices, only the way they are conveyed.