An Interview With Meta-Organizer Rachel Myers

Many Railsbridge chapters have a dedicated organizer who arranges all the
events. The San Francisco chapter, which puts on far too many events for a
single organizer, takes this principle one step further and has a
“meta-organizer”.

I interviewed Rachel Myers, the meta-organizer for the San Francisco
Railsbridge chapter, to talk about what it is that she does.

“A ‘meta-organizer’ matches up venues who can host or sponsor a workshop
with a volunteer that can organize the workshop,” she summarized.

Rachel came across her meta-organizer role organically. Participating in
lots of workshops and social meetups with Railsbridge and Women Who Code,
she became familiar with many of the venues that frequently hosted such
events.

So when a volunteer wanted to organize an event, she knew which venues were
likely to be available and could put the organizer in touch with a contact
person there.

In the past, Rachel sometimes reached out to specific people: “I know
you’ve volunteered at multiple workshops; would you like to organize
one?” But this approach doesn’t work with people who haven’t happened
to show up on her personal radar. So if an upcoming planned event has
no one scheduled to organize, she puts out a general call. A quick tweet from
the Railsbridge Twitter or message to the mailing list usually gets 
at least 5 or 6 responses.

She used to take personal responsibility for keeping an eye on organizers
and making sure everyone was on the same page, but as she’s gotten busier
with her job she’s tried to back away. She now prefers to let people
organize events on their own, confident that they are capable.

That’s not to say that new organizers are left without guidance; first-time
organizers for an event will be paired with an experienced one, or two
first-timers working together will be assigned a mentor to back them up.
This approach helps maintain continuity of knowledge.

And don’t think you have to be a long-time teacher volunteer before putting
on an organizer hat, either. “Sometimes we get people who are, for example,
new to SF and want to make friends, or are starting a new project and want
to recruit. They come to us and say “I want to be involved somehow,” so we
ask them to volunteer at a workshop.” After getting a chance to experience
a workshop in action from a lower-stakes position, they’re welcome to lead
one themselves.

Fresh faces can be great organizers, but it’s a little different for
meta-organizers. “To do a good job as a meta-organizer, you need
connections and long lasting relationships,” Rachel says. But typically
only very few people are willing and able to participate for the length of
time needed to develop these connections; often job responsibilities keep
them busy and limit the amount they can commit to Railsbridge.

When those criteria are met, however, the reward is high: “The process is
one person talking to one person, which is very compelling. If someone says
‘I need you to do this,’ the person will say ‘Okay!’ The problem is that
it’s a huge investment for the person doing the asking if they have to do
it every other week.”

But someday this investment might be no longer necessary.

What’s ahead? 
Rachel envisions an “exciting future” where individuals felt comfortable
reaching out to venues on their own: “If everyone who wanted to get
involved with Railsbridge saw it as their job to, for example, ask
Indiegogo if they would host a workshop, then there would be no single
point of failure. At the moment, if I’m busy, it doesn’t happen.”

She noticed that, with all documentation of workshop planning happening via
a chain of emails, nobody who might want to volunteer could see that it was
happening. So she experimented by creating issues in the Railsbridge
organizing repository
so that the documentation was in the open.
But the outcome was not entirely what she expected.

“I thought people would think, ‘Oh yay! There’s a place where I can sign
up.’ But it turns out it’s very intimidating to sign up to volunteer by
commenting on an issue.”

She suggests a hybrid process where anyone can take the initiative to sign
up to organize events, but people are also invited by another to do that
signing up. And that other person shouldn’t always be the
meta-organizer—there should be a community effort of encouraging people
and making them comfortable to step up.

“I would love a world where other people were empowering people to get
things done. Everyone at this meeting should be able to tell people ‘I need
you to organize a workshop! Here is the process, here is the step-by-step
guide, here is the checklist!”

And in fact, those documents already exist! The Railsbridge Cookbook is an
incredibly thorough guide to running a workshop. “Maybe too thorough,” Rachel
admits. “Maybe people don’t read it.” Too thorough is better than insufficiently
thorough, of course. And it’s a wiki, so anyone inspired can step up and
streamline it or create a summary version.

Really, Railsbridge seems to have the same philosophy as wikis in general:
anyone and everyone has the power to step forward and contribute. And if
that’s not enough, everyone also has the power to tell their friends, “I
want you to do this.” Right now that task may mainly fall to Rachel,
but there’s no reason it has to.

An Interview With Meta-Organizer Rachel Myers

Patterns of Resilient Leadership

RailsBridge was founded by a group of people who were experienced with open source. With intention and thoughtfulness, we applied open source practices to the creation of teaching events. In the past five years, RailsBridge has spread widely across the globe, spawning new workshops in other languages and other locations. We have strong patterns of enabling new leaders to step up and make change. We must be thoughtful on how we support those leaders to create a resilient organization.

The Power of Decentralization

“The Starfish and the Spider: The Unstoppable Power of Leaderless Organizations,” strongly influenced how I thought about the early patterns of the RailsBridge organization. The book highlights the research of Tom Nevins, a cultural anthropologist specializing in Native American tribes of the Southwest. The introduction tells a powerful story about how, in 1519, the powerful centralized Aztec civilization was more easily and quickly conquered by Cortés, than the Apache tribes which withstood the Spanish for hundreds of years — a contrast of centralized vs. decentralized organizations:

A centralized organization is easy to understand. Think of any major company or governmental agency. You have a clear leader who’s in charge, and there’s a specific place where decisions are made (the boardroom, the corporate headquarters, city hall). Nevins calls this organizational type coercive because the leaders call the shots: when a CEO fires you, you’re out. When Cortés ordered his army to march, they marched. The Spanish, Aztecs, and Incas were all centralized, or coercive. Although it sounds like something out of a Russian gulag, a coercive system is not necessarily bad. Whether you’re a Spanish general, an Aztec leader, or a CEO of a Fortune 500 company, you use command-and-control to keep order in your organization, to make it efficient, and to function from day to day. Rules need to be set and enforced, or the system collapses…

Decentralized systems, on the other hand, are a little trickier to understand. In a decentralized organization, there’s no clear leader, no hierarchy, and no headquarters. If and when a leader does emerge, that person has little power over others. The best that person can do to influence people is to lead by example. Nevins calls this an open system, because everyone is entitled to make his or her own decisions. This doesn’t mean that a decentralized system is the same as anarchy. There are rules and norms, but these aren’t enforced by any one person. Rather, the power is distributed among all the people and across geographic regions. (Brafman & Beckstrom, Locations 254-268)

Emerging Leaders

On reflection, I believe the title of the book is misleading. The so-called leaderless organizations actually have very strong leadership; however the leaders are chosen in ways that are independent of a traditional hierarchy, power is distributed, and leadership can emerge from any individual. The book describes many different organizations with non-hierarchical leadership models. The Apache tribe model of leadership is particularly inspiring, leading to resilience in the face of genocidal attackers.

Instead of a chief, the Apaches had a Nant’an—a spiritual and cultural leader. The Nant’an led by example and held no coercive power. Tribe members followed the Nant’an because they wanted to, not because they had to… Coercion is a foreign concept. The Nant’ans were crucial to the well-being of this open system, but decentralization affects more than just leadership. Because there was no capital and no central command post, Apache decisions were made all over the place. A raid on a Spanish settlement, for example, could be conceived in one place, organized in another, and carried out in yet another. You never knew where the Apaches would be coming from. In one sense, there was no place where important decisions were made, and in another sense, decisions were made by everybody everywhere…

Not only did the Apaches survive the Spanish attacks, but amazingly, the attacks served to make them even stronger. When the Spanish attacked them, the Apaches became even more decentralized and even more difficult to conquer. When the Spanish destroyed their villages, the Apaches might have surrendered if the villages had been crucial to their society. But they weren’t. Instead, the Apaches abandoned their old houses and became nomads. (Brafman & Beckstrom, Locations 269-289)

Working with Allies

Another path to a decentralized organization can stem from leveraging an existing network. The book highlights abolitionist, Granville Sharp, who worked with the Quakers to abolish slavery. He did not lead an organization from the top down, but rather activated an existing network from its edges. This is an effective paradigm that is embedded in the RailsBridge model where we ally with corporate and community groups to achieve our goals. However, we must look at his presentation as a cautionary tale. As someone who was for many years an active member of the Society of Friends (aka Quakers), I found it a little disturbing that the authors positioned the Quakers as a “platform” for Sharp’s abolitionist goals, largely ignoring the fact that slavery is inconsistent with the core tenets of the religion and the many activists within the Society of Friends who worked to highlight the hypocrisy and change the dominant paradigm. There is great strength when we tap into a like-minded network. If there exists a group that share values, but has not yet seen the light, then our ideas can spread like wildfire. We must be conscientious in crediting that organization with the creation of that network, the strength of its core values and openness to change.

Eric Ries, who named the entrepreneurial movement “Lean Startup,” is quick to point out that many people were practicing the art for many years. He catalyzed a movement by naming it, creating connections and a space for people to share their success stories and evangelized other people’s success as well as his own. When we tap into companies that seek to create a diverse workplace that is consistent with their own values, we should honor their initiative. Our incredible growth and strength can attributed to the openness and support of the Ruby community, where we had our start, as well as generations of women and people of color who came before us. When new organizations are inspired by our model, get their start at one of our workshops, or leverage our open source software and processes, we cheer them on and tell their stories.

Step Up, Step Back

We should not strive to be a leaderless organization, but rather one where any individual may step up and become a leader without seeking permission or being granted authority. I believe that every person has leadership potential, and every role within our organization, every volunteer task, allows people to practice and demonstrate leadership.

Open source documentation about the structure of the organization is intended to serve as an invitation for anyone to step up. We have such big problems to solve that there is plenty of work to go around. We have infinite possibilities for leadership roles. However, even an open process can appear opaque from the outside — documentation is important, but not sufficient. Each experienced leader must also invite new people to step into a leadership role, then step back into a mentoring role. When the new leader steps up, we have the opportunity to take a rest or step up to a new challenge. We seek to include a persistent, open invitation in documentation and presentations, and augment that message with in person communication.

Patterns of Resilient Leadership

Internet Pioneer Estrin to Speak at RailsBridge Fundraiser

Internet pioneer and Silicon Valley leader Judy Estrin will be the keynote speaker at an event hosted by Railsbridge, a San Francisco-based non-profit focused on fostering diversity in tech, and Galvanize, a startup ecosystem for digital entrepreneurs. Tickets available:

April 7th, 2104:
    6pm VIP dinner
    7:30 Main Event with Judy Estrin
Galvanize Theater, 543 Howard Street, San Francisco

portrait of Judy Estrin Estrin has co-founded eight technology companies and served as the CTO of Cisco Systems as well as on the boards of directors of The Walt Disney Company and FedEx Corporation. While at Stanford, she was a member of the research team, led by Vint Cerf, that developed the initial TCP protocols. She was involved in the early standardization efforts of the Ethernet and a key player in developing the commercial local area network and internet markets.

She will share stories from the early days of the Internet, from the invention of TCP/IP in an academic setting, to creating one of the first commercial local area network systems, to building companies that defined the infrastructure for the World Wide Web of today. Estrin will also share some thoughts about the state of innovation and the internet looking forward.

The event will raise funds for RailsBridge, with matching funds to be provided by Vail Resorts. Galvanize CEO, Jim Deters, was selected to participate in the Vail Ski Challenge and selected RailsBridge as its non-profit partner.

Reserve your spot at the SF event now, and you can also support us by voting for our team on the Vail Ski Challenge Facebook app — you can vote every day! Up to 2000 votes increases the donation to RailsBridge at the end of the challenge.

Internet Pioneer Estrin to Speak at RailsBridge Fundraiser

SF Game Development Workshop

Almost 20 people, mostly women and a few men, crowded into TrueCar‘s conference room. Many thanks to Chris Lichti who responded to a last minute text message and Jeremy who stayed late at the office. Thanks also to Nike for supplying food & drink, Women Who Code who got the word out, connected us to Nike and helped with last minute logistics.

Phoenix Perry from the Code Liberation Foundation taught a hands-on workshop in 2d game programming with Unity. It was great to have an event where experienced programmers could dive in and learn a new environment and programming language — everyone had coded before, but most were new to C#.

At the beginning of her talk, Phoenix reviewed the history of computer programming — from a field that was almost exclusively female to the strange shift to the male-dominated industry we see today. Almost half of gamers are women, and I’m excited about what Code Liberation is doing to bring more women into the exciting world of game development. Normally they teach a series of classes in C++ and open frameworks, and graduates have gone on to develop and publish games.

How did we bring this exciting new movement to San Francisco?

These kinds of simple, yet powerful teaching events do not need months of planning or complex logistics — just like Women Who Code, RailsBridge, ClojureBridge, PyLadies, or any of the other grassroots coding communities, we can make this happen in any major city and in quite a few smaller locales that have a few passionate coders willing to teach. I’m delighted to share the simple and powerful story about how the community came together to support the Code Liberation crew and made this happen.

Late Sunday night, I got a message from an old friend introducing me to Phoenix Perry:

Sarah, Phoenix runs an organization, The Code Liberation Foundation (http://codeliberation.org) to teach women to program games for free… They are in SF this week at the Game Developer Conference and Phoenix is speaking. However, despite the fact that only 4% of game developers are women, they refused their proposal to teach a free workshop for minority voices in games. Persistent, they are still looking for a place where they can run a free workshop. Do you know anyone in SF who might host them?

What kind of person travels across the country to speak at a conference and instead of just going to the parties after a long day at the conference volunteers to teach a group of strangers a new coding skill for free? I do that. So does Desi, Mary, Renee, Sarah and so many other people who have spread RailsBridge far and wide. And here’s someone who wants to come to our town and teach the skills that she knows. How could I say no?

It was heart-warming how the community came together. I decided to reach out to Women Who Code whose thriving community has a lot of experienced developers who write code for all kinds of platforms. Alaina Percival’s quick response was simply to create a meetup event and make me the host so I could fill out the details. There were all sorts of shenanigans in getting the event to happen, as you might expect when you plan an event in 4 days with a loose collection of people communicating via email, twitter, and text messages. With community support, we can be resilient and move fast.

Were you sorry you missed the event? Would you like to see one like it happen again? All the code and teaching materials are on github. I’ll bet Pheonix would be up for a remote teacher training, and we may have some would-be teachers lurking… or could it be you?

SF Game Development Workshop

Galvanize picks RailsBridge for Vail Ski Challenge!

We are very excited to announce that Galvanize has picked RailsBridge as their beneficiary for the Vail Ski Challenge. Galvanize, which runs gSchool, has hosted many Colorado workshops and has been very supportive of our efforts there. They are opening offices in San Francisco and New York City, where we have active chapters.

The future of employment is increasingly digital and skills-based. At Galvanize and gSchool we have a created an immersive learning environment for efficiently equipping new workers with relevant and immediately employable software programming skills. We are excited to partner with RailsBridge who share our passion for diversifying the talent base by creating educational programming and a community to support women in the field of software programming.
        — Jim Deters, Galvanize CEO

We believe that Galvanize is very mission aligned, and we are excited to work together to increase diversity in tech, so that people of all backgrounds can feel welcome and comfortable in our industry.

Please support us by voting for our team on the Vail Ski Challenge Facebook page — you can vote every day! Up to 2000 votes increases the donation to RailsBridge at the end of the challenge. There will also be some ski events which will help raise money for RailsBridge. We’ll send out more info as we have it!

Galvanize picks RailsBridge for Vail Ski Challenge!

RailsBridge as Passion Project

GitHub has a fabulous documentary series interviewing women in tech about their “passion projects.”  Rachel Myers has been an inspiring leader in the San Francisco RailsBridge community.  We’re delighted that she chose to speak about RailsBridge as her passion project:

She also writes about RailsBridge as a “starfish” organization — a big part of her contribution to RailsBridge has been in thinking about how to scale the organization in a way to make it resilient, while still preserving the ability for volunteers to step forth at any point, from any where, and make amazing things happen.

RailsBridge as Passion Project

Bridge Foundry: what’s in a name?

From its inception, RailsBridge was specifically technology agnostic. The TeachingKids project, for example, was taught using Ruby, Javascript and Arduino. Our outreach workshops offer full-day curricula each for HTML, CSS, JavaScript, Ruby, and Rails.

Yet the organization name did not adequately express that technological diversity. Many of the projects inspired by RailsBridge opted to select names that better reflected their communities and activities. PyStar, Scala Crash Course, OpenHatch, Boston Python Workshops, PyLadies, Confident Coding JS, etc.

In pursuing 501(c)(3) status to allow for tax deductible donations, the RailsBridge team decided to create a new parent organization that would be focused on the broad charter that RailsBridge has always worked toward.  With our general fund, we can help people who want to start a new activity with their tech or in their region. RailsBridge will continue to focus on the outreach workshops that have so successful.

This new entity needed a new name. Volunteers collaborated on generating dozens of suggestions. In the end, it was easy to find consensus.

Why Bridge is a good part of the name?

It is a concise way to convey what we’re about. The many initiatives of RailsBridge are about “bridging the gap.” The second RailsBridge guideline reads: “Bridge the gap from aspiring developer to contributing community member, through mentoring, teaching, and writing.” We also bridge gaps across communities, between people who have access to tech & skills and people who do not, between people who feel excluded and people who live & breath this stuff with joy. It’s about forging connections. It was not seen as a requirement that RailsBridge and the umbrella org share common parts of the name — that is a “nice to have.”

Why Foundry is a good part of the name?

We selected SchoolFactory as our fiscal sponsor, and created this new umbrella organization because we want to support the self-replicating nature of what we do.  Applying an open source model to the curricula and the workshop organizing materials and patterns has worked really well to spread workshops across the globe.

“Foundry” speaks to creation.  Miriam-Webster’s definition is “the act, process, or art of casting metals.”  We feel like this work we do is a bit of an art. It is certainly a process.  Every interaction is unique.  We value the difference between people and celebrate each workshop as a unique gathering of volunteer teachers and students. The people we teach (or recruit as teachers, TAs and mentors) go forth as individuals who have leveled up their skills, increase diversity in the tech industry, and contribute their own individual talents to the world. Also the workshops which are created in other locations and targeting other communities are each different — we encourage volunteers to take the materials and ideas and make something that works for their situation within pretty broad guidelines.

Foundry also makes us think of “founder” — every workshop organizer is a founder, and many of us are involved in tech startups where we are very much seeking to change thinking about what kinds of people are tech founders. Diversity fosters innovation.

We also like the word “found” in the name. Each of our projects is composed of “found” objects: a small section of time, bits of contributed skill, tons of open source software and documentation. It reminds us of the “stone soup” nature of our first Boston workshop.

Continuity with our History, Bridge to Our Future

The Bridge Foundry name maintains connection to our first three years. We’ve held over 100 outreach workshops around the world, and they’ve become most closely identified with the RailsBridge name. It’s important to us to maintain a link to that name. So the workshops devoted to Ruby on Rails will continue to be known as
“RailsBridge”, honoring its unique history as the first bridge that this foundry of ours created.

The name Bridge Foundry provides flexibility for naming the existing frontend and Ruby curricula, as well as emergence of more. The Bridge Foundry organization can flexibly embrace its roles as both foundry and foundation for Bridge building projects with potential names such as as RubyBridge, JSBridge, iBridge, PyBridge, ArduinoBridge, or any others we might imagine. Of course, we welcome projects under any name.  RailsMentors (which is for more than just Rails) and the TeachingKids project will continue under the Bridge Foundry umbrella.

Thank you to all for your support and passion over the years. We hope you like the Bridge Foundry name as much as we do.

Bridge Foundry: what’s in a name?