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

Naming methods

More than local variable naming, instance variable naming, and most constant naming, method naming is probably the most important naming in Ruby. The only other naming that is roughly as important is class and module naming. However, in general, there are significantly fewer classes and modules than methods, so you will be dealing with method naming more often.

The Ruby core team recognizes the importance of good method naming, and sometimes there are Ruby features that are considered desirable by the core team but are not accepted into the language, simply because a good method name has not been proposed for them.

One reason why method naming is so important is that method names are difficult to change without breaking backward compatibility, at least if the methods are public. Another reason is that method names have a large effect on the understandability and user-friendliness of the code, especially if they are called often.

In Chapter 3, Proper Variable...