mark 's Profile

By designing carefully and focusing on what you must do rather than how you'll do it, you eliminate the vast majority of getter/setter
methods in your program. Don't ask for the information you need to do the work; ask the object that has the information to do the work for you. Most accessors find their way into code because the designers weren't thinking about the dynamic model: the runtime objects
and the messages they send to one another to do the work. They start (incorrectly) by designing a class hierarchy and then
try to shoehorn those classes into the dynamic model. This approach never works. To build a static model, you need to discover
the relationships between the classes, and these relationships exactly correspond to the message flow. An association exists
between two classes only when objects of one class send messages to objects of the other. The static model's main purpose
is to capture this association information as you model dynamically.

A reusable API or object-oriented framework is, in many respects,
a domain-specific language. Given this, Wirth's classic admonition
that language design is better done by a single guiding intelligence,
rather than by a committee, applies.