Refactoring: Improving the Design of Existing Code by Don Roberts, John Brant, Kent Beck, Martin Fowler, William Opdyke

Refactoring: Improving the Design of Existing Code Don Roberts, John Brant, Kent Beck, Martin Fowler, William Opdyke ebook
Format: pdf
Page: 468
Publisher: Addison-Wesley Professional
ISBN: 0201485672, 9780201485677

€Any fool can write code that a computer can understand. Refactoring is about improving the design of existing code. It was the first I've read related to “clean 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. Also consider reading Martin Fowler's “Refactoring: Improving the Design of Existing Code”. Fowler, Martin, Brant, John, Opdyke, William and Roberts, Don (1999): Refactoring: Improving the Design of Existing Code. One of the great books I read about refactoring was, “Refactoring: Improving the Design of Existing Code”, this book is unbelievable, I recommend everyone to read it. The next book I'll probably get, since I have heard good things about it, is “Refactoring: Improving the Design of Existing Code”. I started with the “Clean Code” book by Robert Martin since I was on a limited budget. It changed the way I am writing code. 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. Refactoring is the process of changing a software system in such a way that it does not alter the external behavior of the code yet improve its internal structure. Being part of this Don't use design patterns for the sake of design patterns: Good developers love writing crafty, intelligent code. (ed.) (2001): Human-Computer Interaction in the New Millennium.