Book Image

Polished Ruby Programming

By : Jeremy Evans
5 (1)
Book Image

Polished Ruby Programming

5 (1)
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

Learning how syntactic consistency affects maintainability

In general, if a single programmer is maintaining the code, whether the code is syntactically consistent or not does not matter. All that matters is that the programmer who wrote the code can read it. In general, programmers tend to write code in a way that makes the most sense to them, even if it may not make the most sense to other programmers. If you are the sole maintainer of the code, you should write the way that feels most natural to you, because that is probably the most productive approach.

However, when multiple programmers are working on the same code, syntactic consistency may become more important, depending on where on the poet-philosopher spectrum each programmer working on the code is. If all of the programmers working on the code lean more toward the poet side of the spectrum, syntactic consistency may still not be important.

However, if a significant portion of the programmers working on the code lean...