Planet Argon

Our CEO, @robbyrussell, is the host of a new podcast produced by the Rails Foundation called On Rails. The show explores real-world decisions that go into building, maintaining, and scaling Ruby on Rails applications. onrails.buzzsprout.com/2462975/episod…

What starts as simple reporting can quietly become the slowest part of a Rails app. Join our 30-minute Planet Argon LIVE webinar with Sergiu Truta next week to learn how to build efficient, maintainable reports with Rails. bit.ly/4bgqAzP

We talk a lot about helping Rails apps evolve instead of starting over. This e-course shows how. Join us! bit.ly/3SSrpCR

🚀 🎉 WOW! Brian Middleton just hit 15 years at Planet Argon. Fifteen years of being delightful, versatile, and dependable. To celebrate, we commissioned a custom skateboard just for him, made by a REAL artist (not AI 😊). Thanks for being with us on this crazy ride, Brian! 🛹

Some software can’t be paused. When your system is in daily use, the work has to happen while everything keeps moving. bit.ly/4auLpHa

Our CEO, @Robbyrussell, built a tool called Clarion that analyzes a ticket and surfaces relevant context from Jira, Confluence, and GitHub. Then it suggests clarifying questions before development even starts. He wrote up the full breakdown on his blog. bit.ly/3OE2eY2

Inherited a Rails app with years behind it? Maintainable Rails is our free course on stewarding and improving legacy code. Join the community! bit.ly/3SSrpCR

A rewrite was planned. Newspaper Club was preparing for a Shopify migration, and their internal dev team was transitioning out. But... their Rails app still needed to work. So they brought us in to keep things steady. But was a migration really necessary? bit.ly/3YJAwd8

Heeeey, check out @planetargon's CEO, @robbyrussell, wearing the first-ever Ghostty astronaut tee! commitgoods.com/products/ghost…

We’ve got a little capacity opening up for short-term engagements. This is for teams who feel… off. Not broken. Not failing. Just disconnected. You’re shipping, but it feels like you’re living inside decisions made years ago. You want to take advantage of what modern Rails, Laravel, or your framework of choice can do now… but the path isn’t obvious. Or maybe your team is experimenting with tools like Claude Code, but everyone is using it differently. No shared language. No guardrails. Lots of potential. Very little alignment. That’s the gap we tend to step into. We help teams: - Reconnect with their existing codebase - Make pragmatic upgrades without the rewrite fantasy - Get developers on the same page about modern workflows, including AI-assisted ones - Turn “we should probably…” into an actual plan Good software doesn’t need to be replaced. It needs direction. No link below. If this resonates, I trust you’re clever enough to find us.

A rewrite isn’t just a plan. It’s a permission slip. To postpone. To ignore. To stop caring… just a little. That drift adds up. More here: blog.planetargon.com/blog/entries/t…

What questions "should" we be asking about maintaining mature apps? Our CEO, Robby Russell, recently appeared on the "Overcommitted Podcast" to chat about sustaining software projects, killer docs/testing habits, and nailing work-life balance in tech. bit.ly/4kicUqZ

Years of decisions live inside long-running systems. Throwing that away is rarely the smartest move. Good software deserves a second act. Not a reset button. bit.ly/4rtnCgu

Wish I could make it this year, but I have a scheduling conflict. Was one of the BEST conference experiences when I attended in 2024. Delighted to have @planetargon sponsor it and will have a few of our 🇧🇷 engineers attending.

Ruby 4.0 marks a new chapter for the ecosystem. For teams running mature Rails apps, it’s also a moment to ask: Is our app ready for its next act? A code audit helps teams understand what's happening in the codebase without the guesswork.

Your Rails app doesn’t need a fresh start. It needs consistent care. The Maintainable Rails email course delivers one useful improvement each week. You'll learn to ask the right questions to implement the simplest changes that make the biggest impact. bit.ly/3SSrpCR

Ruby 4.0 landed quietly over the holidays. Along with it came Ruby Box, performance improvements, and a familiar question: “What is this going to break?” We took a close look at Ruby 4.0 to discover what changed, why it matters, and how to upgrade safely. (Link in comments)

We’re not here to tear things down or declare everything broken. We believe in stewardship, helping teams evolve the systems that matter. Good software doesn’t need a rescue. It needs a thoughtful path forward.

Support shouldn't feel like outsourcing. We want collaboration to feel natural. Like having another steady pair of hands... not a vendor across the ocean. When communication feels easy and progress feels shared, the work moves more steadily.

Take a little time to reflect on your year: bit.ly/3GGrbdU