Over the past few months, a few of us at Planet Argon have been experimenting with Claude Code on real client Ruby on Rails projects. Not demos or greenfield apps, but the kind of long-lived codebases where a backtrace can eat forty-five minutes before you even understand the call chain.
The part that surprised us is how often some of those debugging sessions now wrap up closer to ten minutes.
We’re not ready to make big claims. But we’ve developed enough of a feel for when to reach for it, which model to use, and how to keep it from making a mess of your codebase that it felt worth writing down.
The guide covers things like model selection (Sonnet vs Opus and when to switch mid-session), RSpec and Minitest workflows, debugging with error monitoring payloads, and how we’re structuring CLAUDE.md without turning it into a dumping ground. It’s written for developers who are skeptical of the hype but curious enough to run an experiment.
👉 Claude Code for the Semi-Reluctant, Somewhat Curious Ruby on Rails Developer
The engineers on your team who’ve already started experimenting with tools like this probably have a small head start. The gap closes quickly once you see where they actually help.
