> I don't like this philosophy as it often leads to stagnation in patterns and ways of working that seep into newer systems. The rule isn't "don't introduce ch

> I don't like this philosophy as it often leads to stagnation in patterns and ways of working that seep into newer systems. The rule isn't "don't introduce change", it's "be consistent". Using the example from the post, if you want to use a different method of doing auth that simpler the "be consistent" rule means you must change the way auth is done everywhere. Interestingly, if you do that the negatives he lists go away. For example, if the global auth mechanism handles bots specially, you will learn that if you are forced to change it everywhere.