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



Download eBook




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


Guided by Tests” location 1258; M. After refactoring some code, make sure your test cases still pass and write new test cases where necessary. Fowler, “Refactoring: Improving the Design of Existing Code” location 3320; B. Refactoring, I got influence when I read Martin Fowler's book on Refactoring: Improving the Design of Existing Code. The first place prize will be a copy of Refactoring: Improving The Design Of Existing Code, an Ubuntu Mug, an Ubuntu 10.04 LTS install disc, and a Mun pen. In this post I'll discuss some of the disadvantages of modules, and suggest that Ruby programmers should see them as a method of last resort for code sharing only after carefully considering alternative approaches such as creating classes. 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. Being part of this Don't use design patterns for the sake of design patterns: Good developers love writing crafty, intelligent code. Certainly, I just realize how important it becomes when we maintain the code. Martin, “SRP: The Single Responsibility Principle”, http://www.objectmentor.com/resources/articles/srp.pdf. We recently launched a challenge that invites Safari Books Online subscribers to write a book or video review and in exchange for their review, we'll enter.