Encapsulate that which varies
m |
|||
| Line 5: | Line 5: | ||
When writing software, have a look to see what might vary in the future, and plan for it. Do not attempt to add the functionality (see [[keep it simple]]), but use interfaces/encapsulation to allow any future functionality to added easily. | When writing software, have a look to see what might vary in the future, and plan for it. Do not attempt to add the functionality (see [[keep it simple]]), but use interfaces/encapsulation to allow any future functionality to added easily. | ||
| + | ==Conflicts== | ||
| + | *[[You ain't gonna need it]] | ||
==See Also== | ==See Also== | ||
* [[Don't expose mutable attributes]] | * [[Don't expose mutable attributes]] | ||
Revision as of 08:17, 5 October 2008
"The only constant is change"
It is almost certain that at some point in time functionality of any program will need to change. It is very hard to predict specifics of future requirements, but is easier to predict what parts of the system might change. These parts that may change should be hidden behind interfaces (ie Encapsulated) to help minimize the effects caused by changes in these parts. A simple, every-day example is an instance variable hidden behind a getter and/or setter. As long as the rest of your system is programmed to the interface you are "hiding" behind, variations in the components will have no effect outside of themselves.
When writing software, have a look to see what might vary in the future, and plan for it. Do not attempt to add the functionality (see keep it simple), but use interfaces/encapsulation to allow any future functionality to added easily.
