Growing Object-Oriented Software, Guided by Tests Quotes

“incremental development can be disconcerting for teams and management who aren’t used to it because it front-loads the stress in a project.”
― Steve Freeman, Growing Object-Oriented Software, Guided by Tests (Addison-Wesley Signature Series

“One Domain Vocabulary A class that uses terms from multiple domains might be violating context independence, unless it’s part of a bridging layer.”
― Steve Freeman, Growing Object-Oriented Software, Guided by Tests (Addison-Wesley Signature Series

“How can we hope to catch all the configuration options in an entire system? At some level we can’t, and this is at the heart of what professional testers do.”
― Steve Freeman, Growing Object-Oriented Software, Guided by Tests (Addison-Wesley Signature Series

“Fred Tingey, a colleague, once observed that incremental development can be disconcerting for teams and management who aren’t used to it because it front-loads the stress in a project. Projects with late integration start calmly but generally turn difficult towards the end as the team tries to pull the system together for the first time.”
― Steve Freeman, Growing Object-Oriented Software, Guided by Tests (Addison-Wesley Signature Series

“We’re making the smallest number of decisions we can to kick-start the TDD cycle, to allow us to start learning and improving from real feedback.”
― Steve Freeman, Growing Object-Oriented Software, Guided by Tests (Addison-Wesley Signature Series

“But Sometimes Ask”
― Steve Freeman, Growing Object-Oriented Software, Guided by Tests (Addison-Wesley Signature Series

“Encapsulation is almost always a good thing to do, but sometimes information can be hidden in the wrong place. This makes the code difficult to understand, to integrate, or to build behavior from by composing objects. The best defense is to be clear about the difference between the two concepts when discussing a design. For example, we might say: • “Encapsulate the data structure for the cache in the CachingAuctionLoader class.” • “Encapsulate the name of the application’s log file in the PricingPolicy class.” These sound reasonable until we recast them in terms of information hiding: • “Hide the data structure used for the cache in the CachingAuctionLoader class.” • “Hide the name of the application’s log file in the PricingPolicy class.” Context independence tells us that we have no business hiding details of the log file in the PricingPolicy class—they’re concepts from different levels in the “Russian doll” structure of nested domains. If the log file name is necessary, it should be packaged up and passed in from a level that understands external configuration.”
― Steve Freeman, Growing Object-Oriented Software, Guided by Tests (Addison-Wesley Signature Series

“Composite Simpler Than the Sum of Its Parts The API of a composite object should not be more complicated than that of any of its components.”
― Steve Freeman, Growing Object-Oriented Software, Guided by Tests (Addison-Wesley Signature Series

“One must learn by doing the thing; for though you think you know it, you have no certainty, until you try. —Sophocles”
― Steve Freeman, Growing Object-Oriented Software, Guided by Tests (Addison-Wesley Signature Series