Agile Principles, Patterns, and Practices in C# (Robert C. Martin Series)

by Micah Martin

Welcome changing requirements, even late in development.Agile processes harness change for the customer’s competitive advantage.

Refactoring is the practice of making a series of tiny transformations that improve the structure of the system without affecting its behavior.

A task is something that one developer can implement in 4–16 hours. The stories are analyzed, with the customers’ help, and the tasks are enumerated as completely as possible.

single change causes a cascade of subsequent

Fragility Fragility is the tendency of a program to break in many places when a single change is made.

Immobility A design is immobile when it contains parts that could be useful in other systems, but the effort and risk involved with separating those parts from the original system are too great.

When the design-preserving methods are more difficult to use than the hacks, the viscosity of the design is high. It is easy to do the wrong thing but difficult to do the right thing. We want to design our software such that the changes that preserve the design are easy to make.