> When you read the code you need to know what it does, not what the programmer had intended, then, and only then, will you stand any hope of fixing bugs. I'm

> When you read the code you need to know what it does, not what the programmer had intended, then, and only then, will you stand any hope of fixing bugs. I'm talking about being a user/caller of code, not attempting to fix it. Of course you need to know the innards if you're going to fix it, but needing to know all the implementation details in order to even call a piece of code is counter-productive. It's needlessly time-consuming and it violates the concept of separation of concerns.