We Are the Ruby Community ## Opening (Hook) Raise your hand if you’ve ever: - Used Ruby at work - Used a gem you didn’t write - Googled a Rails error - Listened to a Ruby podcast - Attended a Ruby meetup or conference Now keep your hand up if you’ve ever felt like you weren’t really part of the Ruby community. (Pause.) Look around. Most of the room. That gap is what I want to talk about. Because all of you are already participating in Ruby. But a lot of you don’t feel like you belong to the community around it. --- ## The Misconception A lot of developers think of community like this: - At the top: core team, maintainers, speakers - In the middle: contributors - At the bottom: everyone else That model isn’t wrong. Influence exists. Visibility exists. But it leads to a bad conclusion: “If I’m not at the top, I’m not really part of it.” That’s the mistake. Because community isn’t defined by visibility. It’s defined by participation. --- ## What Actually Sustains a Community The parts you see: - conference talks - popular gems - well-known maintainers Those matter. But they’re not what keep the system running day to day. What actually sustains it: - someone asking a question in a GitHub issue - someone answering it - someone leaving a helpful comment on a PR - someone improving one confusing line of documentation - someone sharing a fix they found Those interactions happen constantly. They’re small. They’re mostly invisible. But they’re the majority of the activity. --- ## Concrete Example (Rails) You hit a weird bug in Rails. Something like: - a Turbo frame not updating - a callback firing twice - a validation behaving unexpectedly You Google it. You land on a GitHub issue. There are three comments: - someone describing the problem clearly - someone else adding reproduction steps - someone suggesting a workaround No one in that thread is famous. But that thread saved you hours. That *is* the community. --- ## My Entry Point When I started writing Ruby, I didn’t know anyone outside of the three people in my office. No meetups. No local community. But I kept hearing about this “amazing Ruby community.” And I remember thinking: “Where is it?” So I went looking. There was a podcast hosted by [Jason Swett](chatgpt://generic-entity?number=0). I reached out and asked if I could join as someone asking questions from a junior perspective. He said yes. That was my entry point. Not because I had expertise. Because I participated. --- ## Reframing Contribution For a long time, I thought contribution meant: - maintaining a gem - contributing to Rails - speaking at conferences Those are real contributions. But they’re not the only ones that matter. What I was good at was asking questions. And it turns out: Good questions are high leverage. They: - expose confusing parts of the ecosystem - create searchable knowledge - help other people with the same problem --- ## Where People Get Stuck The barrier isn’t technical. It’s internal. Developers think: - “I’m not experienced enough” - “Someone else probably knows this already” - “My question isn’t good enough” These show up at every level. Not just beginners. I’ve seen senior engineers hesitate to: - open an issue - ask a question publicly - share something small Because it doesn’t feel “important enough.” --- ## Senior-Level Participation If you’ve been writing Ruby for years, participation shifts. It’s less about asking. More about clarifying. Examples: - explaining a confusing Rails behavior in a GitHub comment - reviewing a PR and leaving a clear explanation, not just “LGTM” - documenting a tradeoff you made in a real system - replying to a question you’ve seen 10 times before That work compounds. Because experienced context is rare. --- ## Consuming vs Participating Most developers stop at consumption: - reading blog posts - watching talks - using gems Participation is one step further: - asking - responding - documenting - sharing The difference is small. But the impact is not. --- ## Small Actions That Matter This is what participation actually looks like: - opening a GitHub issue with a clear reproduction - adding context to an existing issue - improving documentation - sharing a small Rails tip - thanking a maintainer for a fix - answering a question in Slack or Discord None of these require authority. They require engagement. --- ## Local and Offline Participation It doesn’t have to be online. It can be: - a small meetup - a coffee with another developer - a monthly Zoom with someone building in Rails You don’t need a large audience. You need consistent interaction. --- ## A Better First Step If you want to start: - pick a gem you use - find something that confused you - either: - open an issue describing it clearly - or send a short thank-you to the maintainer That’s enough. You contributed. --- ## Why This Matters More Now We’re in a different era. Tools from companies like [OpenAI](chatgpt://generic-entity?number=1) can generate code instantly. Boilerplate is cheaper. Syntax is less valuable. But AI doesn’t replace: - context - judgment - shared understanding - real-world edge cases That still comes from people. From conversations. From participation. --- ## The Shift The value of community is shifting: - from “who can write code” - to “who can share understanding” That’s a different skill. And it’s accessible to more people. --- ## Closing Early in my career, I thought the Ruby community might disappear. People were moving on. Trying new languages. I wondered what would happen. But something else happened. New people showed up. Not as replacements. As participants. And over time, I realized I had contributed too. Not through anything exceptional. Just by showing up. --- ## Final Thought If you’ve ever: - used Ruby - learned from someone else’s code - solved a problem and moved on You’ve already benefited from the community. The only difference between that and being part of it is: whether you give something back. --- (Pause.) Look around the room. This isn’t something happening somewhere else. It’s here. We are the Ruby community.