If you've studied OO or design patterns, you will undoubtedly have heard about the open closed principle (OTC). This is what I believe Steve McConnel is referring to: http://en.wikipedia.org/wiki/Open/closed_principle
/Casper On Dec 12, 12:03 pm, etzel <[email protected]> wrote: > > One principle that Agile Programming advocates have successfully > > established, is that you should not base your current design upon > > speculation about what might or might not happen in the future. Code > > for the requirements in hand. Factor in changes when they happen. > > Agreed. It's just that the author talks about how to predict which > parts will possibly change in the future and how to prepare the code > for that. > > "A good design is prepared for future changes" --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/javaposse?hl=en -~----------~----~----~----~------~----~------~--~---
