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

Recognizing different perspectives of code formatting

You've probably realized that not everyone thinks alike. Everyone is different, and has different opinions on how things should be. Programmers are no different, and in general, for any decently sized module, if you give two programmers the same specification, you will usually get quite different implementations. This isn't a problem or a weakness, it is a strength.

There are many different ways to do almost anything in programming. Some may be objectively better than others, and some objectively worse, but in many cases, given two different implementations of the same requirements, one will be better than the other in some ways, and worse than the other in other ways.

The differences in two different implementations of the same requirements will often vary at every level, from the higher-level design such as class architecture to the lower-level design, such as which expressions are used. For example, consider simple...