Ruby 3.4 introduces some changes to the display of backtrace lines.

So if you've got any code that parses backtraces with regular expressions, you'll likely need to plan for some updates to the parsing logic when upgrading.

Getting closer to a useful "temporary" vs. "permanent" dichotomy for @flipper flags.

Our larger vision is to help make various aspects of flag cleanup and organization more relevant.

For example...

A flag that acts as a long-lived circuit breaker to disable a small piece of functionality to prevent more significant problems? Permanent. Be really sure before deleting.

A flag for a small new feature? Temporary. Clean it up once the feature is complete.

Always fascinated by folks’ workspaces, so here’s my current situation.

What’s yours?

This Sunday, I'll ride for four hours with a couple hundred others to raise money for the Adaptive Sports Center.

Every dollar raised helps ensure that anyone with a disability can take lessons regardless of their ability to pay.

https://www.adaptivesports.org

So until the end of the ride, 100% of the proceeds from sales of Frictionless Generators will go to Adaptive.

Learn something new and save time while supporting a truly life-changing organization.

https://generators.dev

Eight-year ampiversary today.

Still no regrets.

You know that feeling when you obsess over something so trivial that you’re happy but also a bit embarrassed?

Well, my desk and chair wheels match now. Completely and unreasonably stoked about it. (Previous desk wheels broke and provided just enough “justification” to “fix” the mismatch.)

Started a draft of a blog post about organization and structure for different types of code in a Rails application and how to "fill in the blanks" after an app outgrows the core conventions.

I thought it could be a tidy little blog post until I created an outline and started making some notes. This might take a while or several.