Use promo code: OMZNOV15 for 15% off this month.

Solution: shop.planetargon.com/collections/...

reincubate.com/camo/ works great for this, too.

...but I did swap out for a logi MX Brio so i wasn't fiddling with cables throughout the day for typical zoom meetings.

They're even prettier before sunrise!

want to be my "friend" there?

You might even hear from a company you’d love to work for and learn how they put Rails to the test.

And if you already subscribed… have you encouraged your peers to do the same?

Alright, check for your belongings.
All aboard. 🚆

👉 onrails.buzzsprout.com/2462975/follow

Big congrats, Rosa! I know that you were doing a lot of training for that, and I'm glad I had a chance to run with you in AMS. 👏

Nice. Back in 2013, we took a bunch of Rails developers up there during RailsConf. www.flickr.com/photos/plane...

If this hit a nerve, I unpack it more here → robbyonrails.com/articles/2025/10/13/architecture-for-contraction

The engineers who can identify what to consolidate, what to cut, and what to simplify... those are the ones leadership leans on when it really matters.

This isn’t pessimism. It’s strategy.

What could make your team’s 2026 easier?

Every service is another thing to deploy, monitor, and maintain. Every repo is another place where things can break.

The question isn’t how do we scale this?
It’s how do we keep this simple?

We’ve spent a decade optimizing for growth.
It’s time to optimize for longevity.

Now imagine walking into planning with:

> “Here’s how we consolidate deployments, reduce monitoring overhead, and simplify our stack so we’re resilient... no matter the headcount.”

- How long does onboarding really take before someone ships confidently?
- How often do we revisit processes that made sense two years ago but feel like overkill now?
- If three (or ten) people left, could we still ship?