I am scheduling limited speaking engagements for 2017, if you're interested in having me speak at your event let's talk.
I love modules in Ruby: they’re like little folders for your code (ok, well, sometimes they are actually representative of folders in your code). It took me awhile to get comfortable using them, particularly because the concept of
self can be difficult to understand at first. Here’s a quick overview of
self as they pertain to modules in Ruby.
One of my favorite things to do when writing tests is find little ways to write fewer tests but still have the same test coverage. While working on Cryptozoologist, a Rubygem I use to teach gem writing workshops, I utilized a few simple tricks to do this.
Previously, I’ve written about writing a Ruby gem with options for configuration. This is a really great thing to offer your gem users for a number of reasons, but how can we make the interface more helpful to our users? Things like custom error messages for configuration errors and solid testing are two easy ways to get started!
Recently I was working on a Rails application with non-persisted models (aka plain old Ruby objects). We didn’t need a database, which means we didn’t need Active Record either. We opted not to use Active Model, either. We didn’t need most of the stuff...
Last year I was lucky enough to be an MC for a conference in Barcelona, Spain - Full Stack Fest, a combination of Barcelona Ruby Conf and Future JS. While I have hosted single-day events before, this was my first time being an MC for such a big event...