What are the odds to find a beer from your favorite Québec brewery in a random Hakodate bar ?

Yeah, I love having the true local experience as much as the next guy, but that was very scary.

GitHub - Shopify/bundler-ignore-dependency Contribute to Shopify/bundler-ignore-dependency development by creating an account on GitHub.

Also apparently @ufuk.dev did implement a plugin that allow for finer grained overrides: github.com/Shopify/bund...

Perhaps it’s more sensible than force: true

Happy to talk about it in person.

I wrote some more as a way to fight jet lag, hopefully it's still readable 😅: byroot.github.io/ruby/bundler...

I suspect truffle entirely optimized that interpolation out. You might need to “obfuscate “ the two local variables in some way

With the new job, I didn't get much time or energy to blog lately, but I figured I'd use the various downtime while traveling to Ruby Kaigi to write about some of the things I worked on recently: byroot.github.io/ruby/perform...

GitHub - tenderworks/roost: Generate FFI bindings from Rust extensions Generate FFI bindings from Rust extensions. Contribute to tenderworks/roost development by creating an account on GitHub.

It's just a proof of concept, but this is how I wish Rust extensions for Ruby were written: github.com/tenderworks/...

My face when I see a gem with rb-sys in its dependencies

My face when I see a gem with rb-sys in its dependencies

I'm landing Friday, but then I'll pretty much go straight to Hakodate, not really stopping in Tokyo.

I totally get that, but "sidekiq containers" is just as short and more clear than "background job container".

Also it's not a question of threading, SolidQueue does both prefork and threading.

Right, but might also make sense to mention Sidekiq specifically over "background jobs" as while it's dominant, it's not the only option in down.

Why would you be running a single process in job containers? They benefit from CoW just like web processes.

Or are you assuming free version of sidekiq with no preforking?

The show did age incredibly well though. Even without nostalgia, it's still worth a watch in 2026 IMO.

I started the same rewatch just a couple weeks ago, and coughed at the exact same thing 😅

Ruby 4.0.2 Released | Ruby Ruby 4.0.2 has been released.

Ruby 4.0.2 Released www.ruby-lang.org/en/news/2026...

This is a routine update that includes a bugfix in YJIT for NoMethodError on Puma. We recommend upgrading your Ruby version at your earliest convenience.

Reminds me of the old: « XML is like violence » joke.

I guess in practice it’s similar to the shared ban lists you can find on various services.

I'm not even sure if I'd go as far as "idiot". It's impossible for me to guess what the intention is. They may very well have good intentions, but yeah, kinda doesn't give me the motivation to engage.

It somewhat makes sense to me. That gives a place to get updates, changelogs, etc.

There are a few rubygems like that, e.g. rubygems.org/gems/ejson is mostly an empty gem with a Go binary in it.

So far I think reviewing these normally is a waste of my time, if the person on the other end isn't gonna learn anything, why bother? I might as well do it myself. No?

But then what about attribution? Does the LLM wrangler deserve any credit on the final patch?

I'm a bit lost...

But nowadays I get some PRs that are clearly LLM generated, even the feedback I give is clearly directly pasted in the LLM and then sent back to me. It's basically LLM coding by proxy, which begs the question of what to do?

I'm not even sure why I do that, I guess it's a teaching opportunity?

Sometimes it just needs a quick touch up, and I do it myself, as it's not worth the back and forth.

Something I'm not yet clear on how to handle these days is what to do with obvious LLM PRs on Open Source projects.

When a human submit a PR that needs some work, often enough I'll go through rounds of review to progressively get the PR in a mergeable state.

You should yes.

I mean, that somewhat holds true of at least one of his recent predecessors.

Multiprocessing is the most efficient way to serve Rails apps - Balkan Ruby 2026 You’ve been wondering how many threads Puma should be configured to use, or how much cool stuff you’ll be able to build once you’ve migrated to use fibers an...

Process maxing is the way balkanruby.com/talks/32

[Euruko 2025] “Conquering Massive Traffic Spikes in Ruby Applications with Pitchfork” – Sangyong Sim YouTube video by Euruko

TIL that STORES migrated to Pitchfork 🙂

www.youtube.com/watch?v=vOH0...

It depends :) The only way to know is to try.