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

Removing features properly

Removing features sounds like a bad thing for most new programmers, but it is probably one of the happiest moments for experienced programmers. One important thing to understand is that while most users think of features as assets if you are maintaining a library, features are best thought of as liabilities because every feature has a maintenance cost. When you add a new feature to a library you maintain, you are only increasing your future maintenance burden. By removing a feature in a library that you maintain, you are ridding yourself of a liability. This is one reason removing features is one of the happiest moments for experienced programmers.

Obviously, a library with no features is worthless, so an important quality for a library to have is that the features it contains are useful, and not useless, or worse, actively harmful. However, it is often not possible to foresee when adding a feature whether it will continue to be useful in the years to...