|
Loading...
LibraryThing recommendationsMember recommendationsLoading...
won't like
will probably not like
will probably like
will like
will love Sign up for LibraryThing to find out whether you'll like this book.  raymond_and_sarah | Apr 1, 2009 |  I enjoyed the beginning of the book which talked about useful development practices, but the second half of the book was slightly too focused on the author's project. (  ) dvf1976 | Apr 24, 2008 |  no reviews | add a review
Amazon.com Product Description (ISBN 0596008740, Paperback)Prefactoring approaches software development of new systems using lessons learned from many developers over the years. It is a compendium of ideas gained from retrospectives on what went right and what went wrong in development. Some of these ideas came from experience in refactoring. Refactoring is improving the design of existing code to make it simpler and easier to maintain.This practical, thought-provoking guide details prefactoring guidelines in design, code, and testing. These guidelines can help you create more readable and maintainable code in your next project. To help communicate the many facets of this approach, Prefactoring follows the development of a software system for a fictitious client, named Sam, from vision through implementation. Some of the guidelines you'll encounter along the way include: When You're Abstract, Be Abstract All the Way Splitters Can Be Lumped Easier Than Lumpers Can Be Split Do a Little Job Well and You May Be Called Upon Often Plan Globally, Develop Locally Communicate with Your Code The Easiest Code to Debug Is That Which is Not Written Use the Client's Language Don't Let the Cold Air In Never Be Silent Don't Speed Until You Know Where You Are Going (retrieved from Amazon Fri, 24 Apr 2009 07:57:56 -0400) The first test round has been closed. Visit the Open Shelves Classification group for details. |
Popular covers |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Wikipedia in English (1)
Ken Pugh writes with an engaging style that is very easy to read and makes sound suggestions. It would be a valuable guide for new developers looking to broaden their horizons from tools and code. However, there is not a lot that is new in this book and the principles are somewhat introductory for a more experienced programmer. 'Journeymen' programmers would be better served by the Practice of Programming by Kernighan and Pike, or by the Pragmatic Programmet by Hunt and Thomas. (