- Hardcover: 480 pages
- Publisher: Addison-Wesley Professional; 1 edition (October 25, 2009)
- Language: English
- ISBN-10: 0321603508
- ISBN-13: 978-0321603500
- Product Dimensions: 7.2 x 1.2 x 9.4 inches
- Shipping Weight: 1.8 pounds
- Average Customer Review: 3.6 out of 5 stars See all reviews (10 customer reviews)
- Amazon Best Sellers Rank: #1,732,238 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Refactoring: Ruby Edition 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
The Amazon Book Review
Discover what to read next through the Amazon Book Review. Learn more.
Customers who viewed this item also viewed
What other items do customers buy after viewing this item?
From the Back Cover
The Definitive Refactoring Guide, Fully Revamped for Ruby
With refactoring, programmers can transform even the most chaotic software into well-designed systems that are far easier to evolve and maintain. What's more, they can do it one step at a time, through a series of simple, proven steps. Now, there's an authoritative and extensively updated version of Martin Fowler's classic refactoring book that utilizes Ruby examples and idioms throughout-not code adapted from Java or any other environment.
The authors introduce a detailed catalog of more than 70 proven Ruby refactorings, with specific guidance on when to apply each of them, step-by-step instructions for using them, and example code illustrating how they work. Many of the authors' refactorings use powerful Ruby-specific features, and all code samples are available for download.
Leveraging Fowler's original concepts, the authors show how to perform refactoring in a controlled, efficient, incremental manner, so you methodically improve your code's structure without introducing new bugs. Whatever your role in writing or maintaining Ruby code, this book will be an indispensable resource.
This book will help you
• Understand the core principles of refactoring and the reasons for doing it
• Recognize “bad smells” in your Ruby code
• Rework bad designs into well-designed code, one step at a time
• Build tests to make sure your refactorings work properly
• Understand the challenges of refactoring and how they can be overcome
• Compose methods to package code properly
• Move features between objects to place responsibilities where they fit best
• Organize data to make it easier to work with
• Simplify conditional expressions and make more effective use of polymorphism
• Create interfaces that are easier to understand and use
• Generalize more effectively
• Perform larger refactorings that transform entire software systems and may take months or years
• Successfully refactor Ruby on Rails code
About the Author
Jay F ields is a software developer for DRW Trading and a frequent conference presenter. Jay has a passion for discovering and maturing innovative solutions. Jay’s website is available at www.jayfields.com.
Shane Harvie has delivered software in Agile environments in the United States, India, and Australia. He works for DRW Trading in Chicago and blogs at www.shaneharvie.com.
Martin Fowler is Chief Scientist at ThoughtWorks and one of the world’s leading experts in the effective design of enterprise software. He has pioneered object-oriented development, patterns, agile methodologies, domain modeling, UML, and Extreme Programming. His books include Refactoring, Analysis Patterns, and UML Distilled. His book, Patterns of Enterprise Application Architecture, won Software Development’s Jolt Productivity Award and Javaworld.com’s best Java book award.
If you are a seller for this product, would you like to suggest updates through seller support?
Top Customer Reviews
One thing I've learned is that the original is an excellent book, one that probably ranks with "Design Patterns" in practical programming literature. Second, the revising authors added some valuable new material on refactoring in a Ruby environment.
However, "Refactoring, Ruby Edition" seems in some ways to be a sloppy and poorly-edited attempt to cash in on the original. I've found errors on almost every page I've read. It looks as if someone cut and paste the text from the original into a new document, quickly converted the Java examples to Ruby (without testing or review, given some of the errors), and went to press.
My guess is that this was the idea of someone who knows that there are lots of new Ruby programmers who don't have a grounding in Java and are therefore intimidated by the original book. That idea is fine -- Russ Olsen's "Design Patterns in Ruby" seems to be a thorough and careful reworking of that book for a Ruby audience -- but the execution here is really lame. Here are some specifics:
* There are many errors in the code examples and UML diagrams that make them difficult to follow. Until you realize they're errors, you think you're missing something; that kind of thing is tough for novice programmers to identify and correct for. (Ironically, given that the name of the book is "refactoring", these errors aren't in the first edition.)
* The original edition contained illustrative anecdotes about refactoring practice that were clearly presented as call-outs with graphic design techniques like boxing and shaded backgrounds. These design hints are missing from the new edition, and the anecdotes (by other authors) interrupt the text in a confusing way, since they look like a regular part of the text-flow.
* The reader is advised to use the "table in the inside back cover" to identify and address code smells, but there is no table in the inside back cover. There is one in the original edition, however, and it's quite useful. Who knows whether the table was supposed to be included but was forgotten, or was intentionally left out to cut costs?
It seems like no one took another look at this book once the first-draft manuscript was in hand. Martin Fowler and Jay Fields have contributed an enormous amount to the industry, and I'm surprised they would put their names on something this sloppy. Addison-Wesley charges a lot for their books, and they should provide a carefully-edited product in return.
There are so many errors.
Many refactorings start at the end of a page and are immediately cut by the page. It is a very unpleasant reading experience.
Strongly recommend go for the classic JAVA edition.
What i dislike more is that it's obvious the book has been written by different authors:
- Fowler clearly wrote first chapters: writing style is elegant and clear, letting you avid for more.
- starting from chapter 4 you immediately notice Martin has left; by the way i found Sandy Metz work on the topic much more enjoyable (practical object-oriented design in ruby, chapter 9)
- when you start patterns implementation chapters (from 5 on) again you found a less expert writer: information are very useful to me, if you are ready for repetitive/buggy examples (more than once i get confused by same snippet used for both confirming/confuting a particular pattern, until i realize refactoring is a matter of developer's sensibility/experience).
At the end this is a useful volume, but i would have preferred it to be written by a single author:
- Fowler: you'd probably end up having a more conceptual, elegant written book, with less (but relevant) examples
- Fields: the entire book would probably consist of chapters 5-13, being more practical and concise (300 pages long)
Techniques you might already be doing intuitively, and many you probably don't, are described with clear examples and detail helping you convert intuitive decisions into a continuous working method.
This book is a cornerstone for people who is serious about Ruby and want their code to be readable, robust, built from testing, beautiful and easy to change.
And although the purely technical and immediately practical part of the book is of course invaluable, I liked the most the closing chapter 13: “Putting it all together”. I know this is may be only me, and I don’t mind that. ;)
Here is one of the take-away quotes:
“Stopping is the strongest move in the refactorer’s repertoire.”