Exactly. What's nice about this approach is it factors in the "behavioural economics" of developers. As the author puts it... > At the end of the day, everyone

Exactly. What's nice about this approach is it factors in the "behavioural economics" of developers. As the author puts it... > At the end of the day, everyone needs to get work done, and if they see a code-path already being used from 10 places in the code-base despite these soft warnings–it doesn’t seem crazy to introduce another. Even the best person with the best intentions will take a short cut under some circumstances, meaning to fix it later then getting distracted before that happens.