Prefactoring

Pugh, Ken

ISBN 10: 0596008740 / ISBN 13: 9780596008741

Published by O'Reilly, 2005

Our good condition books are generally good for reading but not for gifting or collecting. They could have imperfections such as creasing, fanning, inscriptions, margin notes, yellowing, staining on edge or cover or pages, bumps, scuffs, etc etc (sometimes multiple of these). It's a wide category that encompasses anything that isn't almost-new down to anything that is slightly better than poor. We would NOT recommend gifting Good books - these should be considered reading copies. Our books are dispatched from a Yorkshire former cotton mill. We list via barcode/ISBN so please note that the images are stock images and may not be the exact copy you receive, furthermore the details about edition and year might not be accurate as many publishers reuse the same ISBN for multiple editions and as we simply scan a barcode or enter an ISBN we do not check the validity of the edition data when listing. If you're looking for an exact edition please don't order (at least not without checking with us first, although we don't always have time to check). We aim to dispatch prompty, the service used will depend on order value and book size. We can ship to most countries, see our shipping policies. Payment is via Abe only. Seller Inventory # mon0000037785

Synopsis:

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

About the Author: Ken Pugh has extensive experience in the area of software analysis and design, both as a doer and as a teacher. He's a well-known, frequent conference speaker.

Bibliographic Details

Title: Prefactoring
Publisher: O'Reilly
Publication Date: 2005
Binding: paperback
Condition: Good