Jeff

@marcoroth_ This will be amazing 😍

Now that Herb v0.9 is out, we can start advancing the tooling around `<%= render %>` calls, find unused partials, and build up a graph to understand which partials are referenced from which views! This is also going to be very essential for reactivity.

@marcoroth_ Yes with one option to display inlay if more than X lines between open and close of the tag.

How do we feel about Inlay Hints in HTML+ERB files for closing tags? I'm torn, but the good thing is that most editors allow to disable Inlay Hints if you don't like them. Is this something people would want to use Inlay Hints for? I'd love to hear your opinion!

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

Today's Fizzy deep dive is CSS "While the industry sprints toward increasingly complex toolchains, 37signals is walking calmly in the other direction." zolkos.com/2025/12/03/van…

@adamwathan I use gap often with flex-wrap or grid to ensure consistent spacing when it's needed.

Anyone using `gap` exclusively these days, and never using margins (except for negative margins/overlapping stuff)? I've resisted it because it often introduces extra elements, but curious if anyone has found any surprising benefits.

@jeremysmithco I use fixture for what I call backbone data and easily reusable. I often reach for one-off record, for edge cases, to test creation callbacks. Those one off record creation are often extracted in a helper method.

For Rails devs working with test fixtures, do you have any rules for yourself for when (if ever) you create one-off records within a test, instead of creating new fixtures?

@_st0012 @tekknolagi @k0kubun Congrats 🎉

Excited to share that I became a Ruby committer today! A 10year goal since RubyKaigi 2015. Huge thanks to @tekknolagi for the JIT mentorship and nomination, @k0kubun for years of guidance, and everyone who supported me along the way. Looking forward to improving Ruby and its DX!

What does it take to keep one of Europe’s biggest Rails monoliths running smoothly? In this week’s 'On Rails', @robbyrussell chats with @_beauraF from @doctolib, where 400+ engineers work on a Rails monolith with 3M+ lines of code. Florent shares how they manage 84,000 tests, scale across 10 PostgreSQL databases, and keep Rails upgrades on track. Listen to the full episode here: buzzsprout.com/2462975/episod…

@adamwathan I use a gel wrist rest. I've also tried the wooden keychron one (looks great) but it's too hard for me, becomes painful after few months.

📊 Do you (primarily) rest your wrist on your desk when typing, or float your hands above your desk?

@jespr I share same observation. I can't find any advantage to postgres enum. I always recommend the flexibility of a string field over pg enum.

I really like working with enums in Rails. But I absolutely can't stand how horrid the experience is when it comes to the Postgres side. It's so cumbersome to remove an enum when you realize you went down the wrong path - that in most cases I just leave it 🫠 I might just stop using the enum type in Postgres all together and just stick with enums on the Rails side

After struggling with Actions Runner Controller (ARC) and Kubernetes-based runners, we've switched to Runs-on.com for GitHub Actions infrastructure - eliminating the complexity of managing both Kubernetes clusters and runner scaling. docs.cloudposse.com/components/lib…

@jeremysmithco @pankowecki To me this comment is specific to the example just above it, not general to delegated types. I use delegated types for the two cases mentioned above in same application, and it's working great.

@pankowecki But maybe another use case is this feed/collection situation, where the types can also potentially stand alone. However, that seems to go against the intent of delegated types, from what I see in the docs.

Kasper hits on several things that bothered me about delegated types, but I couldn't articulate. It's nice to see a different take here. kaspth.com/posts/making-r…

For my birthday, I'm giving away five licenses to the Pro version of my Bridge Component library. Repost this with why you love Hotwire Native and I'll DM the winners this week (must be following). github.com/joemasilotti/b…

@_leonvogt This is awesome 👏

Super happy to release Hotwire Native Dev Tools, a lightweight package to enhance the Hotwire Native development experience. Source: github.com/leonvogt/hotwi…

@mhenrixon @dannytipple Does it happen on each request? Or are some requests still fast ?

@dannytipple Yes development mode

Now this is interesting! Suddenly, Rails takes almost a second, but there is no indication of what is slow. Somewhere between request and response is 750ms of???? Where would you start debugging this?

@adamwathan I like the WalkingPad A1 Pro. Though I haven't tried other.

Want to try a walking pad under my desk — there's like 10,000 of these things on Amazon, what's the good one?

@_st0012 Very good

Red-themed RDoc and docs.ruby-lang.org? PR: github.com/ruby/rdoc/pull…

PH launch for @RunsOnRunsOn today! Self-hosted GitHub Actions runners at scale, in your AWS infra. No third parties. 10x cheaper. producthunt.com/posts/runson

@mijustin @TransistorFM Oh yes 😃

Ron Jeffries apologized for inventing Story Points. He then went to call the whole idea of software estimation "evil." Story points is the Emperor's New Clothes. Everyone I've seen—and I mean everyone—uses points as a measure of time: 1 point = 2 hours 3 points = 1 day 5 points = 3 days ... People knows this is what's happening, but nobody says anything. They just pretend they are being "agile." What a cancer. If your company forces you to participate in this charade, I'm sorry.