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)
Section 1: Fundamental Ruby Programming Principles
Section 2: Ruby Library Programming Principles
Section 3: Ruby Web Programming Principles

Adapting and strategizing

The adapter and strategy patterns are often thought of as separate patterns, but in Ruby, they are almost the same pattern, and the naming mostly depends on how the pattern is being applied. The adapter pattern is used for cases where you have one interface that you want to use, but you need to deal with various other objects that implement a different interface. With the adapter pattern, you write an adapter with the interface you want to use that wraps the objects that use a different interface. The strategy pattern is almost the same, except that instead of wrapping an object with a different interface, it implements a different approach for the same type of operation.

Let's say you want to implement a database library that needs to connect to multiple databases. You want the database library to use the execute method for calling an SQL query on each database and getting results back. However, the driver for database M uses the method exec, the...