Chad Lee B.

I've just realized that I've been featured for 4 consecutive weeks! Actively contributing to Rails has been a delightful experience, and I will surely continue to do so. A special shout-out to Jonathan Hefner and @eileencodes for their swift and thorough reviews!

@UltraLinx @brian_lovin Could you make a tweet ( or video ) in a month or so about if going from 6K down to 5K has become an issue for your work. Or is going from 60hz to 120hz worth it more than the 6K resolution. Cheers

The only 6K monitor that actually matches the MacBook displays is the ASUS 6K. But it’s still matte. However it’s the best matte coating I’ve come across where it doesn’t look hazy like others. Still not as crisp as glossy though. I am still sticking with the Studio XDR. Replaced my Pro Display XDR.

Has anyone picked this up? Seems like a great deal for slightly more than the Studio Display and a lot less than the XDR (which I don’t need, but of course the heart yearns)

Here’s how Fizzy implements a really nice data export system. #RubyOnRails

Sometimes I forget how elegant and concise Ruby and Rails is. The usage of concerns, around_action, cookies API, Stimulus conventions, etc. so much conceptual compression. Reading this code made me happy. github.com/basecamp/fizzy…

This week there were 19 contributors to Rails. Thank you to all those whose PRs were highlighted this week: @cocoahero @mctaylorpants @fatkodima @chaadow Check out the full list of the week’s contributors at: contributors.rubyonrails.org/contributors/i…

My C programmer thoughts on Claude+Opus 4.5: 1. Bad at writing code: wrote O(n²) algorithm when O(n) possible. I wouldn't commit its code without review. 2. Responds well to feedback "make this algorithm linear". You have to already be a good programmer to know how the code could be improved. 3. Useful for analysis: "How could this system get into ?" 4. Helps get over procrastination on grindy tasks, like creating a linux sysroot for cross compilation. 5. Makes it cheaper to try different approaches: "change the memory layout to X and use data structure Y, run performance test and compare" 6. Running 1 or more agents in the background while I do other work feels like a superpower. 7. Best when treated like a lawyer's paralegal: you do big brain planning, it does tedium in background, you review, tweak, commit.

Beware of invalid indexes, which you might end up having in Postgres if CREATE INDEX CONCURRENTLY or REINDEX INDEX CONCURRENTLY fails! The database continues to update and maintain those indexes just like regular (valid) ones, adding hidden cost 🤯 Learn more from this great piece: postgres.ai/blog/20260106-…

@HiSaeloun so in this case, it should be somewhat like : `UPDATE 'projects' SET name = "clients".name FROM clients WHERE "clients".id = "projects.client_id"`

@HiSaeloun Thanks for the article. Unfortunately, the SQL in the "after" part is wrong. it's in this form depending on if there is one or many joins. What's in common though, is that `t1` (table1) is always the one you're operating the update on, and `t2` ( table2) is the one used in FROM

No more workarounds! Rails 8.1 brings update_all with joins support to PostgreSQL & SQLite, matching MySQL's long-standing capability. #Rails #RubyOnRails #PostgreSQL #SQLite #Ruby #Programming #BackendDev Read More blog.saeloun.com/2026/01/02/rai…

Ruby threads + a shared Hash = a bug waiting years to happen. A real story from production 👇 evgeniydemin.medium.com/never-cared-mu…

Update: For all my sidekiq dynos, I've disabled eager_load with `config.eager_load = ENV['EAGER_LOAD_ENABLED'].present?`. i've only enabled it on our web dyno. And it just went from 1Gb to 360MB on startup. and with decent work coupled with GC, it stablizes at around 500~600Mb.

anyone else has had his Memory/RAM doubled with ruby 4.0.0 at startup on a rails application. I used to have 510MB on startup. now I got 1010+MB just by launching sidekiq with no queues/no work #ruby #rails (I've disabled YJIT and it saved ~30MB or so)

できました #スマブラSP #ウルフ

@codetrap_dev @GregMolnar @drawkkwast However, I agree, from experience, that it's better to run the stable versions ( 8-1-stable for instance) rather than the latest released version on Rubygems, because unfortunately, versions are not released frequently (there is no strict schedule, like a monthly release or so)

@codetrap_dev @GregMolnar @drawkkwast same (5.2 => 6.0), but since then, Rails improved in that aspect. As @GregMolnar said, more and more companies use rails edge (including myself), so if there is a breaking change it will usually be reported, and the rails team is pretty responsive so that's cool

Ruby 4 is out! github.com/ruby/ruby/rele…

Finally, ruby-lang.org/en/ has a new design.

Check the upcoming storage tracking system for Fizzy by @bitsweat. You always learn when you see Jeremy work. I certainly do: github.com/basecamp/fizzy… I took an initial stab at it by first replicating the approach we use in Basecamp, then refining it based on feedback from Jeffrey Hardy, who has deep knowledge of the problems we've encountered in Basecamp: github.com/basecamp/fizzy… So you can compare three different approaches to the same problem. Open source is cool!

Switched to Difftastic for terminal diffs a few days ago and ever since I've been thinking "how the heck did I not do this sooner" every time I use it.

If your company is moving to SolidQueue from another job framework, I found Andrew Markle's recent RailsConf talk super helpful. One useful technique I learned was to rename the queues based on how long the job might sit in the queue, instead of priority-based or domain-based names. youtube.com/watch?v=lWMYPH…

ActiveStorage Dashboard by @Giovapanasiti is awesome! Deployed it in 5 minutes after testing it to chatwithwork.com github.com/giovapanasiti/…

There is so much wisdom in here. derails.dev/blog/dictators…