I'm still missing it a little I think: the article says that if you remove a bunch of flexibility, like mutable properties, then its harder to make mistakes and

I'm still missing it a little I think: the article says that if you remove a bunch of flexibility, like mutable properties, then its harder to make mistakes and your code is more predictable, right? But like the author mentioned, if you follow good patterns and things like decent naming conventions, and moreover know the language well enough to not make mistakes around things like the purpose of .Equals, then you wont have problems and wont be sacrificing anything either...right?