Book Image

Polished Ruby Programming

By : Jeremy Evans
Book Image

Polished Ruby Programming

By: Jeremy Evans

Overview of this book

Anyone striving to become an expert Ruby programmer needs to be able to write maintainable applications. Polished Ruby Programming will help you get better at designing scalable and robust Ruby programs, so that no matter how big the codebase grows, maintaining it will be a breeze. This book takes you on a journey through implementation approaches for many common programming situations, the trade-offs inherent in each approach, and why you may choose to use different approaches in different situations. You'll start by refreshing Ruby fundamentals, such as correctly using core classes, class and method design, variable usage, error handling, and code formatting. Then you'll move on to higher-level programming principles, such as library design, use of metaprogramming and domain-specific languages, and refactoring. Finally, you'll learn principles specific to web application development, such as how to choose a database and web framework, and how to use advanced security features. By the end of this Ruby programming book, you’ll be a well rounded web developer with a deep understanding of Ruby. While most code examples and principles discussed in the book apply to all Ruby versions, some examples and principles are specific to Ruby 3.0, the latest release at the time of publication.
Table of Contents (23 chapters)
1
Section 1: Fundamental Ruby Programming Principles
8
Section 2: Ruby Library Programming Principles
17
Section 3: Ruby Web Programming Principles

Considering reasons to refactor

There are some common reasons you may want to refactor your library. One of the primary reasons is to simplify your library. Simplifying libraries can take a multitude of different forms, but a couple of common simplifications are realizing that in two or more places in your library, you are making the same change for the same reason. This is a case where you may want to add an abstraction for that type of change. Such an abstraction could be a new method, a new class or module, or possibly a modification of an existing method.

Simplification can also work in the opposite direction, where you have a completely unnecessary abstraction that now makes sense to remove, and then inline the behavior into the places where the abstraction is currently used. This often occurs when the abstraction was created before there was a real need for it, or when the need for it previously existed, but there is no longer a need for it. For example, say you originally...