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
440
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
75
Garden City Rubyconf 2015 Keynote: Race Condition
kaiwren
4
1.5k
Other Decks in Programming
See All in Programming
OUPC2024 Day 1 解説
kowerkoint
0
340
Rails 1.0 のコードで学ぶ find_by* と method_missing の仕組み / Learn how find_by_* and method_missing work in Rails 1.0 code
maimux2x
1
290
オレを救った Cline を紹介する
codehex
16
15k
イベントソーシングによってインピーダンスミスマッチから解放された話
tkawae
1
130
Lambdaの監視、できてますか?Datadogを用いてLambdaを見守ろう
nealle
2
900
ローコードサービスの進化のためのモノレポ移行
taro28
1
170
Goで作るChrome Extensions / Fukuoka.go #21
n3xem
2
2.1k
Google Cloudとo11yで実現するアプリケーション開発者主体のDB改善
nnaka2992
1
180
フロントエンドのチューニングに挑戦してみる
jdkfx
0
110
はじめてのIssueOps - GitHub Actionsで実現するコメント駆動オペレーション
tmknom
7
2k
보일러플레이트 코드가 진짜 나쁜 건가요?
gaeun5744
0
300
Devin , 正しい付き合い方と使い方 / Living and Working with Devin
yukinagae
1
260
Featured
See All Featured
The Language of Interfaces
destraynor
156
24k
実際に使うSQLの書き方 徹底解説 / pgcon21j-tutorial
soudai
176
52k
Fight the Zombie Pattern Library - RWD Summit 2016
marcelosomers
233
17k
VelocityConf: Rendering Performance Case Studies
addyosmani
328
24k
Site-Speed That Sticks
csswizardry
4
430
Raft: Consensus for Rubyists
vanstee
137
6.8k
Fantastic passwords and where to find them - at NoRuKo
philnash
51
3.1k
Agile that works and the tools we love
rasmusluckow
328
21k
Unsuck your backbone
ammeep
669
57k
Designing for Performance
lara
605
69k
Designing for humans not robots
tammielis
250
25k
CSS Pre-Processors: Stylus, Less & Sass
bermonpainter
356
29k
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