Working Effectively with Legacy Code Quotes

“Requirements change. Designs that cannot tolerate changing requirements are poor designs to begin with. It is the goal of every competent software developer to create designs that tolerate change.”
― Michael C. Feathers, Working Effectively with Legacy Code

“Requirements change. Designs that cannot tolerate changing requirements are poor designs to begin with.”
― Michael C. Feathers, Working Effectively with Legacy Code

“Seriously, it is easy to believe that sealed and final are a wrong-headed mistake, that they should never have been added to programming languages. But the real fault lies with us. When we depend directly on libraries that are out of our control, we are just asking for trouble.”
― Michael C. Feathers, Working Effectively with Legacy Code

“The brutal truth is that architecture is too important to be left exclusively to a few people. It’s fine to have an architect, but the key way to keep an architecture intact is to make sure that everyone on the team knows what it is and has a stake in it.”
― Michael C. Feathers, Working Effectively with Legacy Code

“we can’t let “best” be the enemy of “better.”
― Michael C. Feathers, Working Effectively with Legacy Code

“Superficially, Edit and Pray seems like “working with care,” a very professional thing to do. The “care” that you take is right there at the forefront, and you expend extra care when the changes are very invasive because much more can go wrong. But safety isn’t solely a function of care.”
― Michael C. Feathers, Working Effectively with Legacy Code

“Teams take serious chances when they try to make large changes without tests. It is like doing aerial gymnastics without a net.”
― Michael C. Feathers, Working Effectively with Legacy Code

“system will get better as long as people aren’t introducing duplication behind your back. If they are, you can take steps with them short of physical violence,”
― Michael C. Feathers, Working Effectively with Legacy Code

“*brush, Pattern *backdrop)     {      ”
― Michael C. Feathers, Working Effectively with Legacy Code

“The fact remains: Good design is testable, and design that isn’t testable is bad.”
― Michael C. Feathers, Working Effectively with Legacy Code