Head First Design Patterns Quotes

“When you design, solve things in the simplest way possible. Your goal should be simplicity, not 'How can I apply a pattern to this problem.”
― Eric Freeman, Head First Design Patterns

“Take what varies and “encapsulate” it so it won’t affect the rest of your code.”
― Eric Freeman, Head First Design Patterns: Building Extensible and Maintainable Object-Oriented Software

“make sure that we”
― Eric Freeman, Head First Design Patterns

“We’d like to keep things flexible;”
― Eric Freeman, Head First Design Patterns

“A remote proxy acts as a local representative to a remote object.”
― Eric Freeman, Head First Design Patterns

“Composite Pattern takes the Single Responsibility design principle and trades it for transparency.”
― Eric Freeman, Head First Design Patterns

“The NoCommand object is an example of a null object. A null object is useful when you don’t have a meaningful object to return, and yet you want to remove the responsibility for handling null from the client.”
― Eric Freeman, Head First Design Patterns

“two forms of the Adapter Pattern: object and class adapters. Class adapters require multiple inheritance. You can implement more”
― Eric Freeman, Head First Design Patterns

“The large number of acknowledgments is because we’re testing the theory that everyone mentioned in a book acknowledgment will buy at least one copy, probably more, what with relatives and everything. If you’d like to be in the acknowledgment of our next book, and you have a large family, write to us.”
― Eric Freeman, Head First Design Patterns