Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Sign up for free
Keynote at DevOps Days India 2013
February 10, 2014
Keynote at DevOps Days India 2013
My keynote on building and growing technical communities.
February 10, 2014
More Decks by Sidu Ponnappa
See All by Sidu Ponnappa
12 Years of Ruby
Garden City Rubyconf 2015 Keynote: Race Condition
Other Decks in Programming
See All in Programming
Modern Web Apps with Spring Boot, Angular & TypeScript
Named Document って何？
Keep Your Cache Always Fresh With Debezium
How useEvent would change our applications
Where and how to run UI tests (Droidcon London, 2021)
Go API クライアントの実装 〜Go Conference に載せれなかったTIPS〜
Composing an API with Kotlin (Kotlin Dev Day 2022)
See All Featured
No one is an island. Learnings from fostering a developers community.
From Idea to $5000 a Month in 5 Months
Stop Working from a Prison Cell
Six Lessons from altMBA
A better future with KSS
"I'm Feeling Lucky" - Building Great Search Experiences for Today's Users (#IAC19)
jQuery: Nuts, Bolts and Bling
Code Review Best Practice
Docker and Python
Documentation Writing (for coders)
COMMUNITY: THE FAQ
ME @ponnappa github.com/kaiwren C42 Engineering & TrustedRishta.com
ME Founding moderator: BRUG ! Founding organizer: RubyConf India !
Founding member: Devcamp India ! Member: Barcamp Bangalore, BangPypers, etc. ! ! !
WHY TALK COMMUNITY?
WHY TALK COMMUNITY? Good tech communities create immense value.
Community is a decisive factor in the success of a
technology. ! (or philosophy)
An excellent example is the global Ruby community.
This doesn’t happen “automatically.” This conference is an example.
Creating a valuable community takes commitment.
Creating a valuable community takes resources.
Most importantly, it takes time. Years.
UNDERSTANDING Understanding how valuable tech communities were built help us
replicate those successes.
CREATING VALUE Why, how and for whom?
WHY Entertainment. Money. Effort. Time.
Somewhere, a hacker creates something valuable.
Somewhere, another hacker has the same problem. Even if it’s
Somewhere, a customer is willing to pay for something valuable.
This, and everyone in-between, is the community.
COMMUNITY == ECOSYSTEM
ECOSYSTEM MEMBERS Hackers.
ECOSYSTEM MEMBERS Businesses.
ECOSYSTEM MEMBERS Customers.
HOW: MOVING VALUE
Hackers Customers Businesses Fun, Learning, Contracts, Employment. Hackers
Businesses Hackers Customers Businesses Recruiting, Tools, Products, Partnerships, Revenue.
Customers Hackers Businesses Contractors, Tools, Products.
EXCHANGING VALUE A valuable community facilitates bartering value.
BARTERING Bartering depends on trust. Trust depends on reputation.
REPUTATION A valuable community facilitates tracking reputation of its members.
PERSONAL REPUTATION What opinion do we have of each-other?
These two contribute to the reputation of the community as
a whole, attempting to answer the question: ! What is this community good at?
FOR EXAMPLE Math Web apps Scientiﬁc computing
STEP #1 Solve a stakeholder’s problem.
For a new community, it’s easy: Focus on education.
STEP #2 Dedicate time. Be systematic.
Regular meetups. Active lists. ! Keeping to a regular schedule
STEP #3 Identify and promote contributors.
Remember, it’s about reputation and value. Hackers that educate. OSS
contributors. Businesses that contribute money or meet up space. Customers that swear by your technology.
STEP #4 Identify the value chain. Who are the stakeholders?
How do they beneﬁt?
STEP #5 Marketing. Stakeholders don’t always realise how much they
can beneﬁt from actively participating. ! Help them understand. Bring them into the fold.
STEP #6 Facilitate bartering value. Help members of the ecosystem
work together. Reputation and transitive trust is critical.
STEP #7 Encourage face-to-face interaction. The internet is nice, but
meeting people is great for trust.
BE WILLING TO PASS ON THE BATON STEP #8
A NOTE ON PATIENCE
Communities are never perfect.
Ecosystems naturally seek…
Systems in equilibrium change slowly.
Therefore, communities change slowly.
Most successful communities take years to build.
A NOTE ON CULTURE
The most visible examples are the ones that are followed.
Rude people beget rude communities.
Elitists beget elitist communities.
Nice people beget nice communities.
Personal favourite: MINSWAN Matz is nice, so we are nice.
Nice people make the best value transfer facilitators, IMO.
The larger the community, the more entrenched the culture.
There is no superuser. xkcd.com/149 Be ﬂexible. Avoid ego-trips.
Set the right example, early.
A NOTE ON MARKETING
“Build it and they will come” is a fallacy.
Constantly strive to understand stakeholder problems. Maybe they don’t have
learning resources. Maybe they can’t hire. Maybe they can’t ﬁnd customers.
Express how these problems can be solved. Clearly. Concisely. Rails’
scaffolding demo from 2005.
Communities exist for and because of stakeholders.
Businesses and customers are a part of the community too.
Communities facilitate the barter of value among stakeholders.
Effective facilitation depends on creating trust.
Trust depends on reputation.
Building a reputation takes time. ! (and marketing)
QUESTIONS @ponnappa github.com/kaiwren