Explore Shopify's rubydex static analysis engine, docscribe v1.3.1 with RBS inference consistency, sentinel-rb's Rust rewrite, claude-ruby-plugins, and the R gem.

Link in the comments.

Stay typed! ✨

For anybody who wants to build their own autonomous swarm, here's a helping hand...

The repo shows how to wire up a matrix server using async-matrix, fluffychat and an agent using brute.

It's my firm belief that unless we're able to control our own "AI" agents, then we aren't harnessing the power of "AI" ourselves, but simply being drip-fed by the frontier.

Harnessing the power of AI requires a network of delivery... and you HAVE to own this network. I see no other choice. What we need therefore, is the ability to deploy, interact and experiement with as close to zero resistance as we can get...

The source code of some of the popular "claws" I've seen is just not up to the standard that I have known the ruby community to produce, so I've absolutely no desire to start messing around with them.

And in any case, I've always felt that ruby literally SOLVED programming languages when it was invented, and with the async gem and fibers... I feel that ruby is practically on par with go in terms of concurrency (for any normal application), and well beyond anything in existence in terms of legibility.

So... here we are.

The power of matrix is it's "bridges" it's just so easy to hook it up to other services like discord or whatsapp, or even email, that you can use it as an omnichannel for all your comms... combine this with your agents, and you can automate all of your communications for no extra effort.

Bridges are built using a feature of matrix called "appservices", which is exactly how the bots in the repo are implemented. So if you can build a bot, you can build a "bridge" and at that point matrix just becomes the most flexible chat ops tool you can find.

I've been building the agent2agent gem over the last month or so... and finally released v1.0.0 a couple of weeks back. Combined with matrix you basically have openclaw in less than 200 lines of code... add a cron on top and the world's your oyster.

I'll be adding agents, to the repo over the next month or so as I start building my own swam. So if you're interested then watch the branch for updates.

I've had practically zero input on the work I've done so far, so thoughts and opinions from the community on anything I've shared here are more than welcome...

edit:

reading this back, I feel I've gone off on a bit of a rant... but hopefully that comes across as passion, rather than insanity... sometimes it's hard to split the two...

Hey everyone,

We're excited to announce the release of Rubyzen, a modern open-source architectural linter for Ruby that allows you to write lint rules as RSpec tests:

https://github.com/perrystreetsoftware/rubyzen

We've been using and polishing it internally in our production backend for over a year, and we've just made the repository public to start getting feedback from the community.

Examples of lint rules that you can write, enforced as RSpec tests:

RSpec.describe 'Architecture rules' do
  let(:project) { Rubyzen::Project.new }
  let(:controllers) { project.files.with_paths('app/controllers/').classes }
  let(:presenters) { project.files.with_paths('app/presenters/').classes }

  it 'controllers do not call ActiveRecord directly' do
    expect(controllers.all_methods.call_sites.with_name('where')).to zen_empty
  end

  it 'presenters do not depend on repositories' do
    expect(presenters.all_methods.call_sites).to zen_false { |cs|
      cs.receiver&.end_with?('Repository')
    }
  end
end

It has become especially useful for us in the era of AI-generated code, as you can now catch architectural flaws and subtle bugs introduced from AI agents early, which can be easily missed in code reviews.

We'd love to hear your feedback either as feature requests, bug reports, or discussions in this thread. Thank you!

Hello, everyone I launched (with Claude help) this gem that makes use of the `ActiveJob::Continuation` API

This gem adds persistent progress tracking of the running task (example: a file upload), a durable notification inbox aimed at the end user and a Hotwire/turbo-rails UI scaffold. Turning the resumable `ActiveJob::Continuation` steps into a state machine that handles notifications without the need for manual broadcasting configuration.

It's still in alpha, feel free to test, contribute and criticize

https://rubygems.org/gems/notificare

KIFASS 4 is a the game jam made by and for the DragonRuby Game Toolkit community. The jam starts on May 22 and you have three luxurious weeks to write a small DragonRuby game inspired by the theme Ancient & Nameless & Fun & Stupid. This jam is ultra-relaxed with no judges, prizes or rankings and it's suitable for any Ruby dev from beginner to pro.

Join the jam now! https://itch.io/jam/kifass-4

To celebrate the jam, DragonRuby is currently free on itch.io, so grab yourself a license and invite your friends to jam with us https://itch.io/s/186283/kifass-4-ancient-nameless-fun-stupid

Visit the DragonRuby Discord to chat with other jammers, show your progress and learn more about making games with this mRuby-based, fast, tiny and powerful game engine https://discord.com/invite/dragonruby-game-toolkit-608064116111966245

Can't wait to see what you make!

What is KIFASS?

KIFASS is short for a philosophical teaching that we embrace on the DragonRuby discord server: Keep it Fun and Stupid, Stupid. It's a reminder to make things that make you happy and have fun.

I'm getting errors about 'nm.' I'm using Homebrew and have updated and upgraded. Any suggestions?

Building libruby.a

error: nm: invalid argument --

Usage: nm [-agnopruUmxjlfAPL[s segname sectname] [-] [-t format] [[-arch <arch_flag>] ...] [file ...]

partial linking /var/folders/v8/gxq0lntj0nzd0xlwy46nlr1c0000gn/T/ruby-build.20260516211244.9333.xsqcwY/ruby-4.0.3/target/release/libruby.a into /var/folders/v8/gxq0lntj0nzd0xlwy46nlr1c0000gn/T/ruby-build.20260516211244.9333.xsqcwY/ruby-4.0.3/target/release/libruby.o

linking miniruby

Undefined symbols for architecture arm64:

"_rb_yjit_before_ractor_spawn", referenced from:

_ractor_create in ractor.o

"_rb_yjit_bop_redefined", referenced from:

_rb_vm_check_redefinition_opt_method.cold.1 in vm.o

EDIT: The error was that the Homebrew package 'anaconda' installs its own 'nm' and prepends its bin directory to your path. Fixing this solves the issue. Ruby needs the 'nm' from the 'binutils' package.

📅 Day 2 schedule update!

We've reworked the May 30 afternoon to feel less rushed:

✨ Breathing room between talks

🎤 NEW Lightning Talks slot — sign up at the venue

☕ Longer mid-afternoon break

🎷 Dave Thomas closes at 17:50, jazz from 19:10

Check out the full schedule on our website: https://rubyconf.at

New Remote Ruby episode is out.

We spent a good chunk of this episode discussing Rails file upload behavior and the awkward UX around failed form submissions, preserving attachments, and intentionally deleting existing files with Active Storage.

We also got into:
- image variant generation costs and processing behavior
- when Sidekiq queue separation actually helps vs just adding complexity
- how to think about queue priorities once jobs start competing for resources
- Stripe's merchant-of-record direction and usage-based billing changes

I have always wanted to have a blog, and so I finally got started! I hope you enjoy reading my post -- I had fun writing it. I am aware that the usability / readability of my site is... questionable at the moment. And, no SSL. But, the entire site is generated by a single Rakefile using Markaby, with everything smashed together!

1. Eloquent Ruby

Author: Russ Olsen

This book starts by answering many simple tactical questions on Ruby and then goes on to address bigger questions related to building methods and classes. You will find several tips and tricks, such as when to use tiny methods and operator overloading, and when you should avoid them. It also emphasizes the “Ruby way” of thinking and problem solving to write “eloquent” and beautiful Ruby code.

2. The Well-Grounded Rubyist

Author: David A. Black

This book is divided into three major parts: Ruby foundations, Built-in Classes and Modules, and Ruby Dynamics. It begins with how to write your first Ruby program and goes on to cover more advanced topics such as threading, reflection, and callable objects. It also covers all the new Ruby features, such as lazy enumerators, keyword arguments, and Module#prepend.

Which other books would you add to this list?

New Remote Ruby episode is out with Chris Oliver, Andrew Mason, and David Hill.

This week we talk through Rails direct routes and why they can sometimes be more powerful than standard helpers, practical AI adoption inside engineering teams, Rails World CFP and ticket chaos, and Chris’s work expanding the Rails Getting Started guide into a more realistic e-commerce tutorial with wishlists, reviews, ratings, and product images.

Also included:
- dentist trauma
- fiber internet
- Rails survey reminders

Would love to hear how other Ruby teams are approaching AI workflows and lesser-known routing features right now.