🔖 Bookmarks

The new bearer_token method on the Request object is a nice addition to Rails. It removes boilerplate code and simplifies bearer token extraction. All Rails apps can now access bearer tokens the same way without having to write custom token extraction logic every time and worrying about edge cases.

Tick tock… Act now, or this mess might blow up in your face.

Ruby at the Front Line of Disaster Prevention December 26, 2025 How Tokyo Gas Uses Ruby to Protect Millions of People During Earthquakes Based on the RubyWorld Conference 2025 presentation by Maika…

Tricks to work around nested form elements, for Rails

My digital garden has an entire section with copy/paste code snippets and boilerplates. I use these nearly every day when writing code. It helps me start working faster, and saves me from having to rewrite the same code over-and-over again. I created web component boilerplate years ago. Since then, my approach to writing web component has changed quite a bit. I just updated the boilerplate, adding everything I’ve learned from working on Kelp UI.

Let’s build a fun snow effect for your Rails app using a single Stimulus controller.

Practical ways to make your Hotwire Native app feel right at home on iOS and Android.

Organizing tests for readability.

Upgrading the default data-turbo-confirm with a beautiful, native HTML dialog with animations

What is a sequential scan vs index scan vs parallel scan .... and what is a bitmap heap scan? Postgres scan types explained and diagrammed.

The Fizzy application is a new play on Kanban board and project management. It has a comprehensive test suite focused mostly on unit and integration tests, althought other types of test are also present. The test suite is well-organized and follows Rails conventions with some application-specific patterns for multi-tenancy and UUID handling. Can we find more than that?

The new LLM world is very exciting, and I try to experiment with the new tools when I can. This includes building agentic applications, one of which is my personal accounting and invoicing tool - that I wrote about previously As part of that effort I started experimenting with RubyLLM to have some view into items in my system. And while I have used a neat pattern for referencing objects in the application from the tool calls - the Rails Global ID system - it turned out to be quite treacherous. So, let’s have a look at where GlobalID may bite you, and examine alternatives and tweaks we can do. What are Rails GIDs? The Rails global IDs (“GIDs”) are string handles to a particular model in a Rails application. Think of it like a model URL. They usually have the form of gid://awesome-app/Post/32. That comprises: The name of your app (roughly what you passed in when doing rails new) The class name of the model The primary key of the model You can grab a model in your application and get a global ID for it: moneymaker(dev):001> Invoice.last.to_global_id Invoice Load (0.3ms) SELECT "invoices".* FROM "invoices" ORDER BY "invoices"."id" DESC LIMIT 1 /*application='Moneymaker'*/ => #<GlobalID:0x00000001415978a0 @uri=#<URI::GID gid://moneymaker/Invoice/161>> Rails uses those GIDs primarily in ActiveJob serialization. When you do DebitFundsJob.perform_later(customer) where the customer is your Customer model object which is stored in the DB, ActiveJob won’t serialize its attributes but instead serialize it as a “handle” - the global ID. When your job gets deserialized from the queue, the global ID is going to get resolved into a SELECT and your perform method will get the resulting Customer model as argument. All very neat. And dangerous, sometimes - once LLMs become involved.

Accidentally committed secrets to Git? Learn how to safely and permanently remove sensitive data from your Git history using git-filter-repo — the modern,...

In this post, we'll build a Markdown editor using Rails.

A step-by-step path to validate your idea fast by defining the problem, testing assumptions, prototyping the critical flow, and shaping a focused MVP you can learn from.

Master Value Objects in Ruby using the modern Data.define class. Learn about immutability, value equality, and how to eliminate boilerplate code for cleaner, safer domain modeling.

A guide to using the ActionMailer after_deliver callback to log emails sent from your Ruby on Rails application

This is my personal site, where I write about Ruby, programming, and any of my varied fascinations.

As Ruby and Rails developers, we often rely on the same familiar set of methods to get things done. The same set of operations are more or…

The post stuck with me. Over the past year and a half, 37signals has released two more products (Writebook and Fizzy) built on the same nobuild philosophy. I wanted to know if these patterns held up. Had they evolved?

Learn how custom elements work in Rails by building an optimistic form. From simple counters to instant UI updates, understand when to use custom elements over Stimulus controllers.

Not a Medium Member read it here…

A code prototype changes everything. When you prototype in code, the thing you are testing is real. It works in the browser. It works on any device. It responds to real-world variables.

Shipping new features on legacy Rails applications requires deep codebase context. The rails-mcp-server gem closes the gap between AI agents and your Rails projects, enabling more relevant code analysis and context aware refactoring suggestions. Whether you're dealing with tech debt in a brownfield application or building new greenfield features, this tool can help you move faster with confidence.

Should a Ruby class do just one thing? Explore the Single Responsibility Principle, cohesion, and when to split classes through practical examples.