Quotes About Encapsulation

Object-Oriented Design Heuristics (1996), Arthur Riel

Extensive traveling induces a feeling of encapsulation, and travel, so broadening at first, contracts the mind.

Just as it is a good practice to make all fields private unless they need greater visibility, it is a good practice to make all fields final unless they need to be mutable.

Sometimes abstraction and encapsulation are at odds with performance — although not nearly as often as many developers believe — but it is always a good practice first to make your code right, and then make it fast.

Once an object escapes, you have to assume that another class or thread may, maliciously or carelessly, misuse it. This is a compelling reason to use encapsulation: it makes it practical to analyze programs for correctness and harder to violate design constraints accidentally.

When designing thread-safe classes, good object-oriented techniques—encapsulation, immutability, and clear specification of invariants—are your best friends.

There will be times when good object-oriented design techniques are at odds with real-world requirements; it may be necessary in these cases to compromise the rules of good design for the sake of performance or for the sake of backward compatibility with legacy code. Sometimes abstraction and encapsulation are at odds with performance—although not nearly as often as many developers believe—but it is always a good practice first to make your code right, and then make it fast.

Silence held the bubble of the world in its grip.

Use a static nested class when the instances of the nested class don't need to know to which instance of the enclosing class they belong. Use an inner class only if this information is important.

Englishmen do love to bury one thing so completely in another that the two can only be separated by force: peanuts in candy, indigo in glass, Africans in irons. Standing

The bones of the face emerge at six, and the soul within is fixed at seven. The process of encapsulation goes on, to reach its peak in the glossy shell of adolescence, when all softness then is hidden under the nacreous layers of the multiple new personalities that teenagers try on to guard themselves.

All the statements inside the class statement run when the class statement itself runs (not when the class is later called to make an instance).

within a class statement only, any names that start with two underscores but don't end with two underscores are automatically expanded to include the name of the enclosing class at their front.

It's hard to figure out what the right amount of hiding is. Fortunately, with Hide Delegate (189) and Remove Middle Man, it doesn't matter so much. I can adjust my code as time goes on. As the system changes, the basis for how much I hide also changes. A good encapsulation six months ago may be awkward now. Refactoring means I never have to say I'm sorry—I just fix it.

Encapsulation is important, but the reason why it is important is more important. Encapsulation helps us reason about our code.

How do I test private methods?" Many people spend a lot of time trying to figure out how to get around this problem, but, as I mentioned in an earlier chapter, the real answer is that if you have the urge to test a private method, the method shouldn't be private; if making the method public bothers you, chances are, it is because it is part of a separate responsibility. It should be on another class.

If the ideology is built on the identity of the organization and the core tenets of the culture, it is an encapsulation of what makes a company unique.

Extensive traveling induces a feeling of encapsulation, and travel, so broadening at first, contracts the mind.