News




You should use the Ruby on Rails logger block syntax
Passing strings to the Rails logger methods (eg. Rails.logger.info(…)) causes unecessary object allocations, and if you’re calling methods to generate data for your log messages then it can cause unecessary CPU work too. In this post I’ll show you...

Railing against time: tools and techniques that got us 5X faster tests
Slow testing is a drag for any project, but can be especially painful for enterprise-level projects operating at a large scale. This can lead to CI lagging, slower deployment times–and a developer experience that is just plain boring. Evil Martian...



Startups on Rails in 2024: my keynote at RailsConf
In 2023, I attended my first RailsConf. I made some new friends and got an overwhelming amount of support. After that experience, I wanted to reflect some of that awesome spirit back and be useful for the community in some way. This is when I noti...

Mid-Year Review: IRB and Rails Console Enhancements in the First Half of 2024 | Rails at Scale
As a core part of the Ruby ecosystem, IRB (Interactive Ruby) is an invaluable tool for developers. With its rapid pace of changes and improvements, staying up-to-date with the latest features can significantly enhance your development workflow. In...

Abusing Rails' content_for to push data attributes up the DOM | justin․searls․co
f you use Hotwired with Rails, you probably find yourself writing a lot of data attributes. This is great, because (similar to HTMX), it makes the DOM the primary source of truth and all that, but it sometimes imposes one of several vexing constra...