This is a great article, thank you very much for writing it. I pretty much agree with all points, except number 9 could probably be "Not challenging the Status

This is a great article, thank you very much for writing it. I pretty much agree with all points, except number 9 could probably be "Not challenging the Status Quo" instead of "Following the Status Quo". Breaking the status quo just for the sake of it would be a mistake, while healthy challenge of status quo with open mindedness to accept to not change anything is probably a better direction. > Areas of code that don’t see commits for a long time are smells. We are expected to keep every part of the system churning. Or it could be an indicator of mature features that were well designed and implemented to minimize future headache: they just work and have very few stable dependencies, if any.