Refactoring: Improving the Design of Existing Code. Don Roberts, John Brant, Kent Beck, Martin Fowler, William Opdyke
ISBN: 0201485672,9780201485677 | 468 pages | 12 Mb
Refactoring: Improving the Design of Existing Code Don Roberts, John Brant, Kent Beck, Martin Fowler, William Opdyke
Publisher: Addison-Wesley Professional
Refactoring - Improving the Design of Existing Code by Martin Fowler, et. I think people see refactoring as a difficult process. It is the process of changing a software system in such a way that it does not alter the external behavior of the code, yet improves its internal structure. 3 thoughts on “Refactoring: Improving the Design of Existing Code (Addison-Wesley Object Technology Series)”. Good programmers write code that humans can understand.” — Refactoring: Improving the Design of Existing Code, by Martin Fowler . Being part of this Don't use design patterns for the sake of design patterns: Good developers love writing crafty, intelligent code. €Any fool can write code that a computer can understand. Design is hard; so improving design of existing code must be hard, as well, right? Sean Kelly "Consultant" April 27, 2013 at 11:27 am. When I first read Refactoring, I believed that tests were a necessary prerequisite before making structural changes to the code. Description: Refactoring is about improving the design of existing code. Over the past few months, I've been working with an Agile Team in two-week sprints improving an existing and quite complicated planning environment that my company has been developing over the past few years. After refactoring some code, make sure your test cases still pass and write new test cases where necessary. Ever inherit a big mountain of nasty code and have to add new features to it? (Refactoring: Improving the Design of Existing Code, Fowler et al, 1999).