Refactoring: Improving the Design of Existing Code ebook download
Par neal roberto le dimanche, juillet 2 2017, 13:19 - Lien permanent
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
Page: 468
Format: pdf
ISBN: 0201485672, 9780201485677
Publisher: Addison-Wesley Professional
El título me pareció sugerente. Martin Fowler, Kent Beck, John Brant, William Opdyke, Don Roberts. Refactoring: Improving the Design of Existing Code. In my short career I have seen entire systems who should have had a major refactoring. In 2003, I published a Perl 5 “translation” of the first chapter of the book “Refactoring - Improving the Design of Existing Code”, Addison Wesley, by Martin Fowler et al., on my website. However, in this new paradigm it isn't that design is ignored, but rather, the design This includes major refactoring tasks [11, 10], and helps to support continually improving the design. After refactoring some code, make sure your test cases still pass and write new test cases where necessary. Refactoring: 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. Refactoring: Improving the design of existing code. Beck, “Refactoring: improving the design of existing code”, Addison Wesley Longman, 1999, pp.238 – 240. Being part of this Don't use design patterns for the sake of design patterns: Good developers love writing crafty, intelligent code. �Certain structures in code that suggest (sometimes they scream for) the possibility of refactoring.” Martin Fowler. In that time, many worthwhile books on the matter of refactoring have been brought to my attention. This book is all about refactoring. But good design is critical to the long-term maintainability of code, and generally speaking, developers are taught to deliver large, up-front designs that consider the 'big picture', not just the features being added.