I was attracted to this book by the title: 'refactoring' and the agile development philosophy are sometimes used as an excuse for insufficent design. So I liked the explicit emphasis on the need to get stuff right the first time.

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. (

)

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 |

date ▼ | votes

Showing 2 of 2

▾Published reviews

no reviews | add a review

▾Other authors

» Add other authors (1 possible)

▾Work-to-work relationships

view history

▾Common Knowledge

You must log in to edit Common Knowledge data.

For more help see the Common Knowledge help page.

Series (with order)

Theory in Practice

Canonical title

Original title

Alternative titles

Original publication date

People/Characters

Important places

Important events

Related movies

Awards and honors

Jolt Award (2005)

Epigraph

Dedication

First words

Quotations

Last words

Disambiguation notice

Publisher's editors

Blurbers

Publisher series

▾References

References to this work on external resources.

Wikipedia in English (1)

Prefactoring

▾LibraryThing members' description

Book description

Haiku summary

▾Book descriptions

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 Thu, 14 Feb 2013 13:41:10 -0500)

▾Library descriptions

No library descriptions found.