> If you follow them you will end up with code that's really nice to read and easier to maintain, and, most importantly, that you can confidently change ...for

> If you follow them you will end up with code that's really nice to read and easier to maintain, and, most importantly, that you can confidently change ...for trivial cases. For more complex, real-world scenarios, these kind of rules need to be applied sparingly, and where needed. Otherwise you get things like too much abstraction and several layers of inheritance, making it difficult to figure out what anything actually does - the opposite of nice to read Uncle Bob et al have some good guidance, but cargo-culting them led to long-lasting, negative effects on some communities, such as Java and C# developers.