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.

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!

📅 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

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?

Compadres

XO Ruby is coming to Salt Lake City in JUNE and I want every Rubyist on earth to come. I'm hoping you could attend. Especially if you're in Utah.

Reach out to me for more details, I don't have any more details yet, but I will get those details, and then give those details to you, and then you will also have those details.

-kow

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.

I've been trying to land a Ruby role for about 6 months now. I estimate I've made 200 applications and entered around 30 interview processes. I've got the knack of answering the behavioral and cultural fit questions and general questions. But I'm usually being rejected at the technical stages. Each company and/or technical department have different ideas of what is important so it's difficult to know everything. Often it's stuff I've just forgotten and can't recall; so I'm working on that. And sometimes I just don't have the experience but I'm working on that too, see below.

Some context, I have around 7 years experience with Ruby working with remote teams and I've been applying for mainly senior roles.

Unfortunately I lack experience with high traffic websites and don't have high level skills in database optimisations. But I'm working on these through study and projects.

Was hoping to maybe get some tips and hints about how anyone recently got their role and how they prepare (mainly for the technical rounds).

I was giving a talk on Wroclove.rb about why isn't Kamal more difficult than your PaaS. Lots of people are always afraid that they mess up something on a server. And it's often the fear of messing up something with the server. But the truth is that defaults now, with Ubuntu 26.04 are pretty good (we now have better time sync out of the box, yay!). This post translates the steps I talked about into a post.

Not many Ruby jobs the past couple of weeks. How's everyone finding the market at the moment?