Refactoring: Ruby Edition, Adobe Reader
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...more
What I liked about it: That it was so easy and fun to read. Usually I dread reading technical books a little, cos I think they will be all dry and a bit boring. I think reading this book helped with that fear. I liked that it discussed the refactorings in context of object oriented de ...more
My only dislike is the way the book is structured. It's so odd... the first few chapters talk about all these different techniques and methods befor ...more
The discussion about the refactoring principles and process are excellent. It ties in well with the explicit mechanics of the refactoring, which is about being able to take small, behaviour-preserving steps.
Some of the examples are suspect though. The authors point out that the refactorings are not designed to demonstrate a business model, but some of the use of Mountain Bike classes just seem way off. Also, while they don't fully factor ...more
It's a great book to have in the office for starting discussions about how a piece of code should look.
I flew through the first 100 or so pages, but the catalogue of patterns stopped me dead. That section of the book deserves to be read in small chunks as you find offending code in your own codebase.
I read the original version in Java but I feel like I got more out of the Ruby version ...more
Favorite quote: How will you know when you are really getting it? When you start to calm down. When you feel absolute confidence that no matter how screwed-up someone left it, you can make the code better, enough better to keep making progress. ...more
You are likely to see new possibilities in your code, even if you have worked with it for years, once you know about the smells and the refactorings that can sterilize them. You may even want to jump in and clean up every problem in sight. Don't. No manager wants to hear the team say it has to stop for three months to clean up the mess it has created. And, well, they shouldn't. A big refactoring is a recipe for disaster. ...more
Goodreads is hiring!
Learn more »