Consequences
The consequences of an object orgy are essentially a loss of the benefits of encapsulation:
- Unrestricted access makes it hard for the reader to reason about the behaviour of an object. This is because direct access to its internal state means any other part of the system can manipulate it, increasing the amount of code to be examined, and opening the door to future abuse.
- As a consequence of the difficulty of reasoning, design by contract is effectively impossible.
- If much code takes advantage of the lack of encapsulation, the result is a scarcely maintainable maze of interactions, commonly known as a rat's nest or spaghetti code.
- The original design is obscured by the excessively broad interfaces to objects.
- The broad interfaces make it harder to re-implement a class without disturbing the rest of the system. This is especially hard when the clients of the class are developed by a different team or organisation.
Read more about this topic: Object Orgy
Famous quotes containing the word consequences:
“Cultivate the habit of thinking ahead, and of anticipating the necessary and immediate consequences of all your actions.... Likewise in your pleasures, ask yourself what such and such an amusement leads to, as it is essential to have an objective in everything you do. Any pastime that contributes nothing to bodily strength or to mental alertness is a totally ridiculous, not to say, idiotic, pleasure.”
—Philip Dormer Stanhope, 4th Earl Chesterfield (1694–1773)
“We are still barely conscious of how harmful it is to treat children in a degrading manner. Treating them with respect and recognizing the consequences of their being humiliated are by no means intellectual matters; otherwise, their importance would long since have been generally recognized.”
—Alice Miller (20th century)
“There is not much that even the most socially responsible scientists can do as individuals, or even as a group, about the social consequences of their activities.”
—Eric J. Hobsbawm (b. 1917)