- Paperback: 240 pages
- Publisher: O'Reilly Media; 1 edition (8 Sep 2005)
- Language English
- ISBN-10: 0596008740
- ISBN-13: 978-0596008741
- Product Dimensions: 23.7 x 17.6 x 1.5 cm
- Average Customer Review: 5.0 out of 5 stars See all reviews (1 customer review)
- Amazon Bestsellers Rank: 1,018,367 in Books (See Top 100 in Books)
- See Complete Table of Contents
| |||||||||||||||
Did you know you can trade in your old books for an Amazon.co.uk Gift Card to spend on the things you want? Visit the Amazon.co.uk Trade-In Store for more details. |
Product details |
More About the Authors
Discover books, learn about writers, and more.
Product Description
Product Description
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
From the Publisher
Cut back on the refactoring time in your projects with new software design process called "prefactoring." This book presents prefactoring guidelines in design, code, and testing, derived from lessons learned by many developers over the years. With these guidelines, you'll create more readable code before you reach the second-guessing stage.
Inside This Book
(Learn More)
Front Cover | Copyright | Table of Contents | Excerpt | Index
Explore More
Concordance
Browse Sample PagesConcordance
Front Cover | Copyright | Table of Contents | Excerpt | Index
Tags Customers Associate with This Product(What's this?)Click on a tag to find related items, discussions, and people.
|
Sell a Digital Version of This Book in the Kindle Store
If you are a publisher or author and hold the digital rights to a book, you can sell a digital version of it in our Kindle Store.
Learn more
Customer Reviews
|
Share your thoughts with other customers:
|
||||||||||||||||||||||
|
Most Helpful Customer Reviews
1 of 2 people found the following review helpful:
5.0 out of 5 stars
Must have book for any Development team,
By Douggy Fresh (London,UK) - See all my reviews
This review is from: Prefactoring (Paperback)
How come now one has reviewed this book before?
Its so good I bought a few to share around my dev team. The basics of the book take the assumption that what if you wrote code that did not need to be 'refactored' after you completed your project. So suppose you wrote highly reusable code in the first place, understood what is a natral target for refactoring, segment that would get reused. What it you thought ahead just a little bit further before you started coding. This book saves you time and money, let along rework costs.
Share your thoughts with other customers: Create your own review
Most Helpful Customer Reviews on Amazon.com (beta) Amazon.com:
3.6 out of 5 stars (20 customer reviews) 34 of 39 people found the following review helpful:
2.0 out of 5 stars
Pure D-lite,
By wiredweird "wiredweird" - Published on Amazon.com
This review is from: Prefactoring (Paperback)
That's "Design Lite." There's a lot of good advice here, summarized in the aphorisms of appendix A. That includes the usual about avoiding "magic numbers," and some good points about using inclusive data types (strings, for example) to hold values with many incompatible meanings. Pugh also noted that "function codes" as method parameters generally cause problems. If there are different functions to perform, implement them as different methods - don't make one method do lots of different jobs according to some selection key. He could have noted, however, that the "function code" is often a bad smell indicating polymorphic behavior that should have been implemented with class polymorphism.
The presentation as a whole just didn't work for me, though. There were lots of little things, like a sloppy misquote of Santayana's famous "Those who cannot remember the past are condemned to repeat it," minor but annoying. The whole conversational, I-said-then-he-said style is too user-friendly for me - by the time the writer finishes piling on all the scripting flourishes, discussion tends to evaporate into fluff. Pugh could have just made his point without chopping it into pieces and mixing in fictional personalities. Much of the good in this discussion was buried under this chatty style, or lost amid the scene-setting details preparatory to the real discussion of planning for extensibility. The technical problems were the big ones, though. In discussing error handling (p.35), he omits mention of the worst sin I know: silently converting a bad value into something you'd rather deal with. He also missed the biggest extensibility problems I've seen in any system, the ones where external data formats change over time. That happens when your 2.0 program reads a file written by the 1.0 version, and the file format has changed. It can also happen when someone creates a version 2.0 file and sends it to a user still running version 1.0. It happens in worse form when your networked application requires that 2.0 and 1.0 versions of the code talk to each other. Face it, you'll never be able to take down the whole production network and force all the servers to run the same rev of protocol. Inter-version interoperability is a must in any major application, and simply not mentioned here. There is good in this book, but it is often hidden under poor organization, weak descriptions, and lack of technical explanation. Beginners may get a bit from this book but, on the whole, I don't recommend it. //wiredweird 12 of 15 people found the following review helpful:
4.0 out of 5 stars
I think the title is misleading,
By Foti Massimo - Published on Amazon.com
This review is from: Prefactoring (Paperback)
I think the title is misleading, the book is little, if any, related to Martin Fowler's seminal work on refactoring, instead, the book is mostly a collection of best practices, much more like "Code Complete" by Steve McConnell. Nothing revolutionary or innovative, but the book reads quite well and provides a nice good walkthrough of a fictional project. Beginners may benefit a lot from this; more seasoned developers may use it as reminder for best practices.
3 of 3 people found the following review helpful:
5.0 out of 5 stars
It's always good to remember the basics,
By Matthew B. Doar - Published on Amazon.com
This review is from: Prefactoring (Paperback)
This book does what it sets out to do: it describes some wise ideas for software design. (If the name of the book bothers you, get a grip: at least it's short.) Some of these ideas may be familiar to experienced developers, in which case it's a well-written refresher. For some of the ideas, this may be the first time you've seen them described in that way, and a different perspective is also useful.
So, what do I like about this book? - The ideas are practical, common-sense ones. - I like the revisiting of a small number of examples, developing them a little more each time as familiar problems with them are identified. - The book sits comfortably in the world of Agile development, but is not rabid about it. - Design diagrams are used sparingly, enough to educate and remind, but not overwhelmingly so. |
|
Customer Discussions
|
This product's forum
Active discussions in related forums
Search Customer Discussions
|
Related forums
|
Listmania!
Look for similar items by category
- Books > Computing & Internet > Digital Lifestyle > Online Shopping > Amazon
- Books > Computing & Internet > Programming > Languages & Tools > Object Oriented
- Books > Computing & Internet > Software & Graphics
- Books > Science & Nature > Education
- Books > Society, Politics & Philosophy > Education Studies
Look for similar items by subject
Feedback
- Would you like to update product info or give feedback on images?
- I am the Author, and I want to comment on my book.
- I am the Publisher, and I want to comment on this book.
|
