Ruby Community Conference: How It Started, What We Learned, and Why We're Coming Back

Ruby Community Conference was never created as a business project. It grew directly out of the Ruby meetups we had been organizing in Warsaw. The first conference edition was not accidental – it took place exactly one year after our very first meetup, as a way to celebrate what had already become a living, growing community.

Those meetups were built around one simple idea: real conversations over polished stage performances. We wanted people to ask questions, challenge speakers, stay longer, and actually talk to each other. That mindset became the foundation of everything that followed.

When we decided to organize a conference, it wasn't about scaling up for the sake of scale. It was about giving that same community more space.

The First Edition: Small, Wild, and Honest

We organized the first edition of Ruby Community Conference in just one month. It seems crazy when I think about it now. It was free, had no long-term roadmap, and no financial expectations attached to it. Our only goal was to do something meaningful for the community we came from.

We invited speakers we deeply respected: Nick, Sergey, Paweł, and Kris – not only for their expertise, but for their contribution to the Ruby ecosystem.

The conference took place in a relatively small venue and yet, it gathered around 110 people. The conference itself was a huge success, but the afterparty that followed was simply epic. It happened in the Visuality office garden, where about 70 people showed up. It was a bit wild, definitely improvised, and absolutely unforgettable.

People stayed long after the talks ended. They asked questions, engaged in discussions, and didn't rush home. That moment confirmed something important: this was never about perfect production. It was about atmosphere, openness, and connection.

One Early Decision That Changed Everything

From the very beginning, we made one decision that shaped the entire conference.

We added workshops.

This came from our internal experience as a company. We had already learned that while talks inspire, workshops are where real learning happens. Presentations can open minds, but workshops give people confidence and practical skills they can actually use later.

From that point on, workshops became the core of the conference, not an add-on.

Growth, Rhythm, and Learning Our Limits

Six months later, we organized a winter edition that attracted around 250 participants. That gave us confidence to establish a rhythm. For the next year, we ran the conference twice a year – summer and winter.

Summer editions were calmer and more community-oriented, but attendance was lower. At the same time, the organizational effort was huge regardless of the edition size. We eventually decided to keep only one edition per year – the bigger one. This made it easier to consolidate costs, avoid constantly adding our own resources, and attract higher-quality speakers who could justify the trip.

Today, Ruby Community Conference happens once a year, in winter. More focused. More intentional. More refined.

What Makes Ruby Community Conference Different

Several principles guide every edition of the conference.

First, we optimize for real conversations. We allow questions, encourage discussion, and don't treat the agenda as untouchable. If something valuable is happening, we accept being a bit late. We prefer a relaxed atmosphere over rigid schedules.

Second, workshops remain at the core. Talks inspire curiosity, workshops turn it into practice.

Third, speakers are curated. Speakers are invited with intention, so the program feels cohesive and rooted in shared values.

Finally, networking and flexibility are first-class citizens. Starting with the fourth edition, we introduced an unofficial pre-conference meetup as a warm-up for the community. After the conference, we organize optional networking activities such as city walks or quests. These are not mandatory, but they give people a chance to stay longer, connect deeper, and experience Poland and Kraków (previously Warsaw) together.

Built for Community, Not for Profit

Ruby Community Conference was never about money.

We come from the community, and that shapes our decisions. We want tickets to stay accessible and sponsorship packages to remain affordable. At the same time, scale changes reality.

What once required a small hall and a garden now means renting museums or cinemas. Depending on the edition, this included a Japanese museum in Kraków with a view of Wawel Castle, or a cinema located in the Palace of Culture and Science in Warsaw. These choices are not about prestige. They are about creating an experience that is attractive both for high-quality speakers and for people who invest their time to attend.

Naturally, this affects pricing, and it is something I still reflect on.

To stay aligned with our values, we made a clear decision: any income beyond what is necessary to organize the conference goes back to the community. All surplus is donated to Ruby Europe, supporting Ruby communities across Europe.

We are also very intentional about costs. We invest in what matters, meaningful venues, great food, and space for conversation, and cut what doesn't. No badges. No t-shirts. No unnecessary extras. Community doesn't need swag. It needs intention.

Sponsorship as Double Support

This is why sponsorship matters.

By sponsoring Ruby Community Conference, companies support the community twice. First, by helping us keep the conference accessible and high-quality. Second, by contributing directly to the wider Ruby ecosystem through our donation to Ruby Europe.

It's not just about visibility. It's about reinvesting in the community many of us grew up in professionally.

What the Community Gave Back

Some of the most important outcomes of the conference never appeared on the agenda.

During the second edition, I spoke with Yauhen, who was disappointed that there were no active Ruby meetups in Barcelona. He wanted to do something, but didn't know how. I told him that I know how and that I would help. That conversation led to the reactivation of Barcelona.rb. Looking back, this moment directly contributed to recognizing the need for broader support for Ruby communities in Europe, which later resulted in the creation of Ruby Europe and the revival of meetups in Madrid, Valencia, Vienna, and other cities. Personally, this is one of the biggest successes of this entire journey.

Another moment happened when John, a speaker from the third edition, approached me during the 4th conference and told me he had landed his dream job. He explicitly thanked us for the opportunity to speak, share his niche topic, and gain recognition within the community. Today, he runs online workshops and helps teams understand the importance of observability.

There are many more stories like this. New products born from conversations between engineers who met at the conference. People who found jobs. A sponsor found a new development team. New open source contributors. Friendships that started over coffee.

None of this was planned.

All of this was enabled.

Why We Keep Coming Back

Organizing Ruby Community Conference takes time, energy, and emotional investment. It has never been easy.

But it changed me.

It helped me overcome fears around public speaking. It taught me how to organize large-scale events, how community marketing really works, and how much impact intentionally created spaces can have on people's careers and lives.

We keep coming back because we believe in communities built deliberately, not accidentally. In depth over noise. In real conversations that last much longer than the conference itself.

And as long as that belief holds, this story is not finished.

Become a part of this story. Learn more about Ruby Community Conference!