There are many indicators that your models have grown too big, but the most indicative is when your model breaks the single responsibility principle. First introduced by software engineer and author Robert Cecil Martin in his book Agile Software Development, Principles, Patterns, and Practices, the single responsibility principle states that… continue reading →
For most Rails developers, a massive benefit of using the Rails framework is the power of its core components, like the dominant Active Record. Acting as the model in the core model-view-controller paradigm that Rails is built around, according to the official documentation, an Active Record is the “layer of… continue reading →
Rails is a powerful and relatively easy to use framework. Its dominant principles heavily emphasize convention over configuration, allowing new Rails applications to be up and running in a fraction of the time for applications created in many other, more verbose languages. However, the simplicity that Rails provides can also… continue reading →
Today we finally come to the end of the journey through our Ruby Exception Handling series. The last, and perhaps most critical, error left to discuss is the Fatal Error, which indicates a severe crash in a Ruby application — something so dramatic that the process couldn’t recover from it… continue reading →
Today our journey through the Ruby Exception Handling series continues with one of the last remaining Ruby errors left to discuss: SystemStackError. This little baby pops up when code gets a little recursion-happy and ends up causing a stack overflow. In this article we’ll examine the SystemStackError in more detail… continue reading →
As we approach the end of our all-encompassing Ruby Exception Handling series, today we’ll be taking a look at the SystemExit error, which is raised whenever the Kernel#exit method is invoked to terminate the current process. In this article we’ll explore the SystemExit exception in more detail by looking at… continue reading →
Today in our continued journey through our Ruby Exception Handling series we’ll be taking a closer look at the ZeroDivionError. As you may suspect the ZeroDivisionError occurs when attempting to divide a number by zero. In this article we’ll briefly explore the ZeroDivisionError in more detail, including where it sits… continue reading →
Next on the docket of our Ruby Exception Handling series is the lovable TypeError class. TypeErrors are fairly simple and are raised when an object that was passed as an argument is not of the expected type. In this article we’ll look at TypeErrors a bit closer and see where… continue reading →
Making our way through the Ruby Exception Handling series we have now arrived at the ThreadError class. ThreadErrors are raised anytime an invalid operation is attempted on a thread, plain and (somewhat) simple! Throughout this article we’ll examine the ThreadError in a bit more detail, looking at where it sits… continue reading →
Moving along through our Ruby Exception Handling series, today we’ll be checking out the SystemCallError and it’s closely associated Errno subclasses. SystemCallErrors are raised during any low-level, platform-dependent exceptions like invalid IO calls and the like. In this article we’ll explore the SystemCallError in more detail, including where it resides… continue reading →
No more searching through log files. Capture every bug and error in your app with just a few lines of code.
Try For Free