Nice :) I think it was a good choice

Find all these recommendations here newsletter.shortruby.com/p/five-ruby...

And don't forget to subscribe to Short Ruby Newsletter -> to get a lot more in your inbox every week.

5️⃣ Avo - Deterministic Mesh Gradient Avatars in Rails

Avo continues to publish on their blog deep dive good tutorials and this one is no exception. Using ChunkyPNG and a bit of math you will generate some very nice mesh gradient avatars with Ruby.

avohq.io/blog/determ...

4️⃣ Jason Swett - RSpec shared examples unmasked

Jason goes over BetterSpec recommendation for using shared examples and builds up an argument for why in testing DRY might not be a good principle to follow.

www.saturnci.com/rspec-share...

3️⃣ Maciej Mensfeld - When Your Hash Becomes a String: Hunting Ruby’s Million-to-One Memory Bug

He explores a puzzling Ruby memory bug, guiding us through clues and insights into Ruby's memory model. It feels like a detective's journey.

mensfeld.pl/2025/11/rub...

2️⃣ Noel Rappin - Ruby And Its Neighbors: Smalltalk

Enjoyed Noel's exploration of Smalltalk, highlighting its innovations and how Ruby borrowed from it. Insightful, especially from someone with professional experience in Smalltalk.
noelrappin.com/blog/2025/1...

1️⃣ Julian Rubisch - An Introduction to Game Development with DragonRuby

An excellent exploration of using Ruby beyond web apps. This post provides enough information to get you excited about having fun with DragonRuby
blog.appsignal.com/2025/11/05/...

Oh I love you setup :) enjoy the coffee!

In some projects, the time spent on testing often outweighs the time spent writing code. Having a clear testing strategy can greatly aid daily decision-making. Despite being a mundane area we often overlook, it can make a significant difference in developer happiness.

The most important part of the test strategy is not about having written the perfect document that outlines it but going through the process of defining it and pinning down decision about how the testing should be.

The test strategy will need to evolve and adapt.

When thinking about using AI/LLMs to generate test cases then you can take the test strategy and trim it down to essence, add some good/bad examples and some tactics and that is your testing guideline for an LLM.

Congrats!

You cand find all these and a lot more inside the Short Ruby Newsletter @shortruby.com

newsletter.shortruby.com/p/edition-156

Matz ( @matz.bsky.social ) hinted that this should be considered a low-level API and there may be plans for a higher-level API in the future. This is exciting, as it could open up more possibilities: bugs.ruby-lang.org/issues/2138...

The proposal that was finally accepted by @matz.bsky.social was suggested by Satoshi Tagomori @tagomoris.bsky.social
bugs.ruby-lang.org/issues/2138...

The discussion about this renaming was initiated by Xavier Noria @fxn.bsky.social sharing good reasons here about why the name should be reconsidered:
bugs.ruby-lang.org/issues/21385