| Short Ruby Newsletter | https://shortruby.com |
| Website | https://allaboutcoding.ghinda.com |
This is not about syntax beauty or elegance. It is about the developers who show up, contribute, and build alongside each other.
Every language claims community matters. Ruby is making it the central identity.
Ruby's new identity statement caught my attention:
"A language where people gather, a site where people are visible."
Source: https://www.ruby-lang.org/en/news/2025/12/22/redesign-site-identity/
In a world where a lot of resources online might be generated by LLMs I find it inspiring that the language choose to position itself a thing "where people gather".
It is not just poetic. It is a statement about what kind of knowledge-building Ruby values.
One of my intentions with the Short Ruby Newsletter was to create an archive for these types of discussions.
So, next time someone suggests that Rails might be the problem at GitHub, here are two people who can confirm it was not.
When working on #goodenoughtesting, I keep three LLM tabs open: Claude, Codex, and Gemini.
I test each prompt against all three to catch where instructions break down. When they disagree, that's where I focus as I want to reliable generate tests.
Adding Amp to the mix soon.
Yesterday I talked with @onurozer about the #goodenoughtesting workshop and where to take it next.
One thing became clear: I need to better communicate what problem it solves and for which teams it works best.
Not just build more content, but explain the value more clearly.
If you use AI to edit your blog posts, always keep the original version.
Not to preserve your mistakes, but to learn what the AI changed and decide what to keep. It also has the side effect of having a collection of writings by you that were never changed by the AI.
Testing isn’t about doing everything. It’s about doing the right things and doing enough of them to sleep well at night.
If you're trying to balance quality, speed, and complexity, risk gives structure to your thinking and clarity to your priorities.
Use risk as a spotlight.
I am working this weekend to finalise the content for the upcoming #GoodEnoughTesting workshop:
- I am trimming a lot of the previous content to keep it to only the essential
- Rethinking the code and exercises I previously used
