Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

112
Building Social Software for the Anti- Social Jeff Atwood stackexchange.com

description

Part II of the original "Social Software for the Anti-Social" presentation, with five more SCARY RULES!

Transcript of Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

Page 1: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

Building Social Software for the Anti-Social

Jeff Atwoodstackexchange.com

Page 2: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

1. Radically lower the bar for participation

2. Trusting (some of) your users

3. Life is the world’s biggest MMORPG

4. Bad stuff happens5. Love trumps money

Page 3: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

Building Social Software for the Anti-Social

Part II

Jeff Atwoodstackexchange.com

Page 4: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo
Page 5: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo
Page 6: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo
Page 7: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo
Page 8: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

Q:

How do you tell an introverted computer programmer from an extroverted computer programmer?

Page 9: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

A:

An extroverted computer programmer looks at your shoes when he talks to you.

Page 10: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

Q:

What do Computer Science students use for birth control?

Page 11: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

A:

Their personalities.

Page 12: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

“But the meek shall inherit the earth …”

Page 13: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

Computers are simple.

People are complicated.

Introverts are writing software to control both. How can this possibly work?

Page 14: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo
Page 15: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo
Page 16: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

Programmers move beyond merely playing the game

They create and design games.

Very, very complicated games.

Page 17: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo
Page 18: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo
Page 19: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo
Page 20: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

Social interactions are scary because

THEY HAVE NO RULES

Page 21: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

Can you define rules for social interactions?

Maybe.

Page 22: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

… or maybe not.

Page 23: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

But…why are social interactionsparticularlyscary for an introvert developer?

Page 24: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo
Page 25: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

All teachers of programming find that their results display a 'double hump'. It is as if there are two populations: those who can, and those who cannot, each with its own independent bell curve.

Page 26: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

“To write a computer program you have to … accept that whatever you might want the program to mean, the machine will blindly follow its meaningless rules and come to some meaningless conclusion.”

Page 27: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

“The consistent group showed a pre-acceptance of this fact: they are capable of seeing mathematical calculation problems in terms of rules, and can follow those rules wheresoever they may lead.”

Page 28: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

Facebook is exactly that: mapping rules to social relationships between people.

Taking what had been scary and unknown, and adding rules and structure.

Page 29: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

Scary Idea #6

Rules can be fun and social.

Everyone loves games, and all games are built on rules. Guess what programmers are REALLY good at?

Page 30: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

Tragic: The Garnering, from Fallout

Page 31: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo
Page 32: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo
Page 33: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo
Page 34: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo
Page 35: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo
Page 36: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo
Page 37: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo
Page 38: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

To play the game, you must accept the rules.

The rules exist to protect the integrity of the game, and more importantly, to keep it fair for every player.

The rules are part of the common good.

Page 39: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

But … what’s the goal of this game?

What is its purpose?

Page 40: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

Scary Idea #7

All modern website design is game design.

Everything’s social, therefore, everything is now a game with rules.

Page 41: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo
Page 42: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

Let’s play the Q&A game. You have a … question. A specific question that can be answered (see rules).

How do you get an answer to your question?

First you must figure out how to ask.

Page 43: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo
Page 44: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo
Page 45: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo
Page 46: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

What is this number and how do I get it to go up?

Page 47: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

What is this number and how do I get it to go up?

Page 48: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

What is this number and how do I get it to go up?

Page 49: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo
Page 50: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

“Stack Exchange is like a well-designed video game. When was the last time you had to read the documentation to play a video game? You don't.”

– Robert CartainoDirector of Community DevelopmentStack Exchange

Page 51: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

You start by walking across the room. Then you learn to pick something up; and then jump. By time you need to, you're already strafing across a catwalk, jumping and spinning 360-degrees while simultaneously firing a beam rifle and throwing two plasma grenades through a window 40 feet away.

Page 52: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

When you get up from the couch after a Halo or World of Warcraft session, what do you have to show for your efforts?

Page 53: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

Whereas on Stack Exchange, you leave breadcrumb trails of your awesomeness for others to learn from and improve on.

Page 54: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

Game: get an answer to your question, by any means necessary.

Metagame: reputation, badges, privileges, peer recognition.

Endgame: improve the internet for everyone.

Page 55: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

The game works in service of both selfish (I need an answer!) and selfless (I need a better internet!) goals.

We’re creating an oasis of high quality, expert Q&A on the internet that can serve as a national park of information: a public resource for all to enjoy and benefit from.

Page 56: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo
Page 57: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

Scary Idea #8

Thoughtful game design creates sustainable communities.

Government is a form of game design.

Page 58: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo
Page 59: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

“It is an invariable principle of all play … that whoever plays, plays freely.

Whoever must play cannot play.”

Everything else is by definition Work with a big W.

Page 60: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

The game never ends.

Actions in the game have consequences and history.

People will remember how you behaved in previous rounds.

Page 61: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo
Page 62: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo
Page 63: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

Permanent death.

How can that be fun?

This is a horribly flawed game design!

Page 64: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

1. You cannot win alone.

2. Individual skill, however great, is always inferior to teamwork.

3. Rash decisions are risky; patience and planning pays off.

Page 65: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

The design of the game forces you to play as a team.

Whether you want to or not!

Page 66: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

The rules make the game work, even with completely anonymous

internet players.

Brilliant.

“All my teammates are my friends”

Page 67: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

It’s an infinite game.Any time, with anyone.

Counter-Strike54k players / day

Page 68: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

Stack Exchangeis my

Counter-Strike

Page 69: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

1. You cannot win without teaching.

2. Individual skill, however great, is always inferior to communication skill.

3. Discussion is risky; sharing research and experience pays off.

Page 70: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

Teamwork:

Advance knowledge of a topic.

For everyone in the world who loves that topic as much as you do.

Page 71: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo
Page 72: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

Scary Idea #9

The community isn’t always right.

Groups aren’t good at predicting the consequences of their collective actions.

Page 73: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

1. You should only ask practical, answerable questions based on actual problems that you face.

Why can’t we have discussions?

Page 74: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

What’s your favorite bicycle?

I use spatulas to turn eggs, what do you use?

Bing is doomed. I’m curious if others feel as I do.

What if Canon merged with Nikon?

COBOL sucks, am I right?

Page 75: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo
Page 76: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

Chatty, open-ended questions diminish the usefulness of our site and push other practical questions off the front page.

If you don’t like these questions, don’t look at them!

Page 77: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

“Don’t look” doesn’t work in real life, either.

Broken windows: others will see, and use what they see as templates for future questions.

Opportunity cost: time spent on discussion is time that should have gone toward sharing actual research.

Page 78: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

Protip: answer the damn question.

What research and evidence can you provide to support your answer?

Page 79: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

Oh yeah? Prove it.

Page 80: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

Your questions should be reasonably scoped. If you can imagine an entire book that answers your question, you’re asking too much.

Why can’t we ask broad questions?

Page 81: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

Q: First let me inform you: I am new to this type of enterprise and in a sense I am looking for all the help that I can get so that I will have a general idea where to start. I have a drawn out plan for the workings of an electronic communication application. Its not that complicated in terms of its usage and function. The impass that I am at has to do with me not knowing how to create this application because of my lack and understanding "how to write a program" using programming language. I have done my homework (undercover market research) and found that ten out of nine individuals would purchase this product if it were available. My second impass is that my funds are at an all time low. So any information woild be most appreciated. Thank You.

Page 82: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

A: Begin by reading a book or two. Come back when you have specifics.

Page 83: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

2. What research, if any, did you do before asking?

What have you tried? What happened when you tried that? How did you attempt to solve the problem?

You gotta do your homework.

Page 84: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

It is unfair to ask others to do all the work.

If you want to play the game, meet us halfway.

Nobody should be more motivated to find an answer to your question than YOU.

Page 85: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

“But this is such a great resource, why can’t I ask just this one question the way I want to?”

Did it ever occur to you that the site is a great resource precisely because we disallow discussions and drive-by no effort questions?

Page 86: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

There are many kinds of games on the internet. We designed ours a certain way to achieve a certain result.

Perhaps you want to play a different game somewhere else on the internet?

Page 87: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

“Innovation is not about saying yes to everything. It's about saying NO to all but the most crucial features.”

– Steve Jobs

Page 88: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

Can you say NO to your users?

(in a nice, educational way of course.)

If not, then you have a problem.

Page 89: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

Scary Idea #10

Some moderation required.

Someone has to protect the community from itself. Why can’t it be you?

Page 90: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

The curse of popularity, aka Bikeshedding.

The more general interest your question is, the more people can see it and answer it – with their unique individual opinions.

Page 91: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

“What is your solution to the FizzBuzz problem?”

“Best Keyboard for programmers?”

“What are some funny loading statements to keep users amused?”

“What easter eggs have you placed in code?”

“What single discovery has given you the biggest boost in productivity?”

Page 92: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

If a question can have infinite answers …

… is it really a question?

… or is it something else entirely?

Page 93: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

“Over on FriendFeed people are telling me ‘we have more conversations.’ That’s true, but the more conversations I got involved in the less I found I was learning.”

-- Robert Scoble

Page 94: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

“How can you close / delete this question, it is hugely popular with the community!”

Popularity isn’t the only metric that matters.

Page 95: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo
Page 96: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo
Page 97: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

“ever since the Open Beta the amount of image macros, memes, rage comics and generally low-quality content hitting the front page has grown to annoying proportions.”

Page 98: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo
Page 99: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

“The problem with image macros and rage comics (besides generally lacking wit or anything genuinely insightful) is that they're quick and easy to digest, and thus tend to get upvoted faster than self posts and actual discussions which take thought and time before an appropriate response can meted out. If you're not careful you end up with something akin to /r/gaming, which is now a burbling, deformed wreck of its former self, with anything remotely resembling intelligent discussion being buried under a sea of vacuous meme-repetition.”

Page 100: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

“This only way this is EVER stopped on reddit is through mod intervention, rule sets, and careful removal of content. So along with this post, please directly contact the mods and hope that they will act to save their subreddit.”

Page 101: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

The goal of moderation is not to punish the community, but to

• Temporarily overrule

• Educate

• Refocus community exuberance on more substantive content

... in other words, to lead.

Page 102: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

Our biggest mistake: not building a meta from day one.

“The place about the place” is where all governance forms and moderators are born.

Page 103: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

Moderation requires power, the power to (sometimes) defy the community to lead it.

Moderation has to scale in proportion to the size of your community.

Therefore, you must give power to regular users: mini-moderators.

Page 104: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo
Page 105: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

It’s a Democracy: moderators are elected by the community.

Page 106: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo
Page 107: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

Moderators are yourPark Rangers

Page 108: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

But elected community moderators are not infallible.

If you have an issue with moderation, bring it up on the meta. Citizens have input into government and the design of Stack Exchange itself.

Page 109: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo
Page 110: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo
Page 111: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

6. Rules can be fun and social.7. All modern website design is

game design.8. Thoughtful game design

creates sustainable communities.

9. The community isn’t always right.

10. Some moderation required.

Page 112: Oredev 2011: Building Social Software for the Anti-Social Part II, Electric Boogaloo

JOIN US!

Help build our park.

http://stackexchange.com