Agile Principles, Patterns, and Practices in C# Quotes

“Abstraction is the elimination of the irrelevant and the amplification of the essential.”
― Robert C. Martin, Agile Principles, Patterns, and Practices in C#

“Design and programming are human activities; forget that and all is lost. —Bjarne Stroustrup, 1991”
― Robert C. Martin, Agile Principles, Patterns, and Practices in C#

“Factories are a complexity that can often be avoided, especially in the early phases of an evolving design.”
― Robert C. Martin, Agile Principles, Patterns, and Practices in C#

“When the I metric is 1, it means that no other component depends on this component (Ca = 0), and this component does depend on other components (Ce > 0). This is as instable as a component can get; it is irresponsible and dependent. Its lack of dependents gives it no reason not to change, and the components that it depends on may give it ample reason to change.”
― Robert C. Martin, Agile Principles, Patterns, and Practices in C#

“It is the perversity of software that a module that you have designed to be easy to change can be made difficult to change by someone else simply hanging a dependency upon it.”
― Robert C. Martin, Agile Principles, Patterns, and Practices in C#

“CRP says that classes that are not tightly bound to each other with class relationships should not be in the same component.”
― Robert C. Martin, Agile Principles, Patterns, and Practices in C#

“If a component contains software that should be reused, it should not also contain software that is not designed for reuse. Either all the classes in a component are reusable, or none of them are.”
― Robert C. Martin, Agile Principles, Patterns, and Practices in C#

“During this design process, we rarely considered whether we were performing analysis, design, or implementation”
― Robert C. Martin, Agile Principles, Patterns, and Practices in C#

“Databases should usually not be considered as a major factor of the design and implementation.”
― Robert C. Martin, Agile Principles, Patterns, and Practices in C#

“So, when and why should we use UML? Diagrams are most useful for communicating with others and for helping you work out design problems.”
― Robert C. Martin, Agile Principles, Patterns, and Practices in C#

“If its dependencies are inverted, it has an OO design. If its dependencies are not inverted, it has a procedural design.”
― Robert C. Martin, Agile Principles, Patterns, and Practices in C#

“Resisting premature abstraction is as important as abstraction itself.”
― Robert C. Martin, Agile Principles, Patterns, and Practices in C#

“We develop features before infrastructure and frequently show those features to stakeholders.”
― Robert C. Martin, Agile Principles, Patterns, and Practices in C#

“Indeed, most of us realize that the requirements are the most volatile elements in the project.”
― Robert C. Martin, Agile Principles, Patterns, and Practices in C#