This one feels good. No more stupid comments at the top of files. At least in one repo.

Happy to share that today I'm starting as senior principal at Intercom!

I've just released json 2.7.3 with some bug fixes and lots of performance improvements: github.com/ruby/json/release… This is my first release after being made maintainer two weeks ago.

I'm working on a blog post about our new out of band GC. Sneak peak:

Not the hack we deserve, but the hack we need: github.com/ruby/ruby/pull/10…

Also one trick I used to track down where some object was allocated from:

I often joke how Shopify's monolith is the true last boss of Ruby. I've just spent 3 days tracking down a weird test failure that turned out to be a parser bug. Millions of lines of code were running fine, only one list was impacted. So easy to miss.

Chilling in Montréal on my way to Rails World.

I forgot to show what a call cache look like. The important part is the `klass`. You check if the cached class is the same as the object you need to call a method on. If yes you have a direct pointer to the method_entry. If it doesn't match, you reset it to that new class.