Magicians never share their secrets. But we do. Sign up for our Ruby Magic email series and receive deep insights about garbage collection, memory allocation, concurrency and much more.
Remember when you were a kid, and you bought those omnibus double edition comics? How magical reading them was? We won't pretend this will be as unforgettable, but we do think we've put together a nice extra-chunky Best-of AppSignal Academy selection for you to read at the beach, the park, or just on a lazy Sunday, that will absolutely make your day.
Here are our top 5 hammock reads:
Almost everything in Ruby is an object and errors are no exception. #dadjokes
rescue, Ruby has more ways to handle exceptions. We'll use the
ensure keywords as well as reraised exceptions to build a resilient web API client.
The post about
retry was super popular last holiday. Its little-known counterpart
redo works similarly, but reruns loop iterations instead of whole blocks.
Like squirrels in a summer forest, the N+1 queries problem is a common, but usually easy to spot nuisance, ehm, performance anti-pattern that's sometimes caused by lazy loading associations.
By nesting cache fragments, views are almost never rendered completely. Even when data changes, most of the rendered pages are served straight from the cache.