edream wrote:
Let me throw out another idea here. The reverse of an 'heroic'
solution would be a 'simplistic' approach. Sometimes simple
guidelines can be surprisingly useful. I am thinking in particular of
the best programming advice ever given to me: namely to make class
methods or functions be as small as possible. At first, this sounds
like simplistic (simple minded) advice, but my experience is that it
is not.
This reminds me of Kent Beck's original book on Smalltalk patterns.
Practically all of them had the effect of limiting the size of classes
and methods. (His general principle was "lots of little pieces".)
--
Don Dwiggins
Advanced Publishing Technology
