Abstract
Software design is not easy-not easy to do, teach, or evaluate. Much of software education these days is about products and APIs, yet much of these are transient, whereas good design is eternal, if only we could figure out what good design is. The author has been struck by one of the underlying principles that leads to better designs: remove duplication. The principle is simple: say anything in your program only once. Stated blandly like that, it hardly bears saying. Yet identifying and removing repetition can lead to many interesting consequences. The author looks at a simple case of subroutine calls. He considers the benefits of design patterns.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
