Because the class you’re reusing is confused about what it does and contains several tangled up responsibilities, it has many reasons to change. It may change for a reason that is unrelated to your use of it, and each time it changes there’s a possibility of breaking every class that depends on it.
- Chapter 2. Designing Classes with a Single Responsibility
- from Practical Object-Oriented Design in Ruby: An Agile Primer
- Publisher: Addison-Wesley Professional
- Released: September 2012
Increase chance of changing (& breaking) the class ... if it does too much.
Share this highlighthttp://www.safaribooksonline.com/a/practical-object-oriented-design/70751/