Welcome to the 53rd issue of Ruby Radar! There are some excellent deep dives into Rails in this issue. Hopefully, it inspires you to do some exploring yourself!
Railsconf is back in person! We sat down live to record awith Jemma Issroff, Brittany Martin, Robby Russel, Andrew Culver, Nicholas Schwaderer, and Colleen Schnettler to discuss everything Ruby on Rails.
This week, I’m joined by Thai Wood for a discussion about incident response, runbooks, unarticulated expertise, mistakes during incident response, and listening to feelings.
Rails is full of “magic”, but if you dig a little, that magic is just some ruby code. For instance there is 1.day.ago, which returns a DateTime object for 1 day ago. Did you ever wonder how does this work? Let’s get to the bottom of it.
Ok! so I got @rails forked and up and running with @github Codespaces, but I have no business hacking away on rails/rails, right? Who do I think I am??
Well, why don't you come with me while I funk around and find out!?
A while back, I ran a Twitter poll about how people debug in Rails (~1400 votes). 82.9% did NOT use a debugger
24.5% printed (here I am). 43.7% launched a console on the spot using binding.{irb,pry}, 14.7% used byebug as a mere console, without using debugger commands.
Tweet
Share