One of the best features of the Ruby programming language is the mixin. It’s a module in Ruby that you can add, or mix into any other class when you want to extend it with new methods.
In this blog series, we’ll detail our experiences with adding Sorbet to a large-ish (> 100k LoC) Rails codebase. In this first post, we’ll add sorbet to the project, and add types to our first file.
Many useful features like syntax highlighting, multiline editing, display documents, enable auto indent, enable save and load history by default are introduced in IRB with Ruby 2.7.
End users attempt to use the software in legitimate but unforeseen ways. The system then rejects their inputs and throws away their data. Finding the software to be an obstruction to work, they then route around it. If we are very lucky, they also complain to us, the developers.
This post isn’t so much of an argument as to why one should be testing in production than an honest analysis of the challenges inherent in conducting these forms of tests.