Accessibility Handbook

This is the eBook version of the printed book. If the print book includes a CD-ROM, this content is not included within the eBook version.

Refactoring–the art of improving the design of existing code–has taken the world by storm. So has Ruby. Now, for the first time, there’s a refactoring workbook that’s been designed from the ground up for the Ruby dynamic language–not adapted from compiled languages like Java or C++.

Refactoring in Ruby gives you all the realistic, hands-on practice you need to refactor Ruby code quickly and effectively. You’ll discover how to recognize “code smells” that signal opportunities for improvement, and then improve your program’s design one small, safe step at a time.

You’ll learn when and how to refactor with both legacy code and during new test-driven development, and walk through a real-world refactoring in detail. The book concludes with several large programs designed to help you practice refactoring in several realistic domains, plus a handy code review checklist you’ll use constantly. Along the way, you’ll learn powerful lessons about designing higher-quality Ruby software: lessons that will help you experience the joy of writing great code–not just occasionally, but constantly.

Refactoring in Ruby will help you

• Identify signs of poor Ruby code design, and systematically improve existing software
• Understand the undesirable consequences of poor code design, and the tradeoffs associated with fixing it
• Recognize why poor code design occurs, so you can prevent it from occurring in your own code
• Master better design techniques that lead to more efficient, reliable, and maintainable software
• Practice analyzing code, so you can become more effective at it
• Fix code that’s too long, large, or difficult to follow
• Ferret out duplication, and express each idea “once and only once”
• Use naming standards that provide a clear mental model for everyone who works with your code
• Improve and generalize conditional logic–and avoid using it as a “weak” substitute for object-oriented mechanisms
• Recognize missing or inadequately formed classes
• Simplify overly complex relationships between classes and their subclasses
• Achieve the right balance of responsibilities amongst objects
• Make your code easier to test and change
• Cope with incomplete library modules, and fix runaway dependencies
• Learn the next steps to take after you refactor
• Choose the right Ruby refactoring tools for your environment