Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Keynote at DevOps Days India 2013
Search
Sidu Ponnappa
February 10, 2014
Programming
0
480
Keynote at DevOps Days India 2013
My keynote on building and growing technical communities.
Sidu Ponnappa
February 10, 2014
Tweet
Share
More Decks by Sidu Ponnappa
See All by Sidu Ponnappa
12 Years of Ruby
kaiwren
0
80
Garden City Rubyconf 2015 Keynote: Race Condition
kaiwren
4
1.5k
Other Decks in Programming
See All in Programming
Ktorで簡単AIアプリケーション
tsukakei
0
110
One Enishi After Another
snoozer05
PRO
0
160
Migration to Signals, Resource API, and NgRx Signal Store
manfredsteyer
PRO
0
120
SODA - FACT BOOK(JP)
sodainc
1
8.8k
Six and a half ridiculous things to do with Quarkus
hollycummins
0
210
エンジニアインターン「Treasure」とHonoの2年、そして未来へ / Our Journey with Hono Two Years at Treasure and Beyond
carta_engineering
0
430
Webサーバーサイド言語としてのRustについて
kouyuume
1
4.9k
『毎日の移動』を支えるGoバックエンド内製開発
yutautsugi
2
290
Server Side Kotlin Meetup vol.16: 内部動作を理解して ハイパフォーマンスなサーバサイド Kotlin アプリケーションを書こう
ternbusty
3
250
品質ワークショップをやってみた
nealle
0
640
釣り地図SNSにおける有料機能の実装
nokonoko1203
0
200
TransformerからMCPまで(現代AIを理解するための羅針盤)
mickey_kubo
7
5.4k
Featured
See All Featured
Easily Structure & Communicate Ideas using Wireframe
afnizarnur
194
16k
YesSQL, Process and Tooling at Scale
rocio
173
15k
Building a Scalable Design System with Sketch
lauravandoore
463
33k
Visualizing Your Data: Incorporating Mongo into Loggly Infrastructure
mongodb
48
9.7k
Faster Mobile Websites
deanohume
310
31k
Automating Front-end Workflow
addyosmani
1371
200k
Fashionably flexible responsive web design (full day workshop)
malarkey
407
66k
BBQ
matthewcrist
89
9.9k
Code Review Best Practice
trishagee
72
19k
How to Ace a Technical Interview
jacobian
280
24k
Optimizing for Happiness
mojombo
379
70k
Designing for Performance
lara
610
69k
Transcript
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.
CAVEAT: IMHO
CREATING VALUE
CREATING VALUE Why, how and for whom?
WHY
WHY Entertainment. Money. Effort. Time.
Somewhere, a hacker creates something valuable.
Somewhere, another hacker has the same problem. Even if it’s
boredom.
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.
FACILITATING BARTERING
BARTERING Bartering depends on trust. Trust depends on reputation.
REPUTATION A valuable community facilitates tracking reputation of its members.
DIGITAL REPUTATION
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 Scientific computing
BUILDING COMMUNITY
GETTING STARTED
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
is critical.
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.
TAKING OFF
STEP #4 Identify the value chain. Who are the stakeholders?
How do they benefit?
STEP #5 Marketing. Stakeholders don’t always realise how much they
can benefit 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…
None
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 flexible. 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 find customers.
Express how these problems can be solved. Clearly. Concisely. Rails’
scaffolding demo from 2005.
IN CONCLUSION
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