“.. the fact that the color values are subtly changing with each release could be problem for your users and the consistency of your application.”

www.zolkos.com/2024/11/30/b...

Upgrading Rails applications to Tailwind 4 www.zolkos.com/2024/11/30/u...

Appreciate @flavorjon.es quick releases of the tailwindcss betas for ruby projects. github.com/flavorjones/...

Found that is was faster to run my Rails test suite with a single core instead of all 16. I wrote a little script that runs the test suite with the same seed from 1 to x cores and then tabulate the result. (this is for 433 tests, 1250 assertions).

imo config/environments/* files should be empty.

The only things in there should be overrides of default values.

eg if force_ssl is true by default in production then it should not be in the production.rb file *unless* I want to override it to false.

I wish I had the motivation to execute app ideas of my own. But I don’t. But executing on a clients or employers project/vision I am 100% on board and motivated and delivering. Anyone else feel like this?

Going to go down the ActiveSupport::Notifications rabbit hole today and see if I can improve the design of my app that has some callbacks that could be better by being event driven.

Do y’all upgrade the ruby version to the latest in your apps as soon as it comes out? Or wait? Or some set cadence?

Who wrote some Ruby today? 👋

Rails 8 is out. Nothing relaxes me more than upgrading Rails versions. It has gotten so much easier over the years.

I’d pay for screencasts of guests opening up their rails apps to pair on upgrades and refactorings.

Eg Here is one hour of replacing sidekiq with solid queue on this 7 year old app.

Wow this is so cool. No politics.

Howdy world