An interesting take on what makes a successful Social site – LBW
“As we move from the era of computing into the era of the Internet, we no longer need to worry about computer-human interaction.” Joel Spolsky told a group of programmers at Google last month. “What we do have to think about [in the era of social networking] is human to human interaction,” he said. And according to Spolsky, to do that, you have to think as an anthropologist does.
Anthropology and the Social Web
“In anthropology it’s very clear that the environment that you create influences people and how they behave”, Spolsky explained. “People will come into the environment and behave according to what you built in certain subtle ways; ways that you probably didn’t think about.”
He points to the Scalinata della Trinita dei Monti, or the Spanish Steps to further his point. “They were built to be stairs,” he said, “from the Spanish Embassy at the base, up to the Trinita dei Monti at the top.” Instead, they’ve become the “living room” for backpackers in Rome. “Partially it has to do with the steps being the perfect comfortable height to sit on,” he said, but also, they provide a fantastic view of the Piazza di Spagna at the bottom.
“This was completely non intentional,” he explained. “Similarly, the user interface you create for your applications will influence how people behave.”
The Nine Building Blocks of Social Engineering
- Voting: Copied from Reddit, via Digg, voting allows people to vote up answers they think are good. Stack Overflow tweaked its voting algorithm, giving the person who asked the question special power to select one answer as the official answer that will rise to the top regardless of what the community voted. The second answer, of course is always the highest ranked community answer.
- Tags: Tags allow users to specify perspective. For instance, Spolsky explained, “you can add that I’m asking this from a VB perspective, not a C# perspective.” Stack Overflow is also customizable with tags, allowing users to specify which technology they are interested in, and typical of most social sites. What is not typical however, is the ability to ignore tags that Stack Overflow has built in.
- Editing: Taking a page out of Wikipedia, Stack Overflow allows users to edit both questions and answers; so answers could get better, rather than becoming “this frozen artifact on the Internet until the end of time,” which is typical of most forum threads.
- Badges: “A soldier will fight long and hard for a bit of colored ribbon,” said Napoleon once upon a time, and so Stack Overflow made the decision to reward its users with badges. Over time, the badges show credibility.
- Karma: People are willing to do for free what they’re not willing to do for small amounts of money according to Spolsky and by offering karma, Stack Overflow encourages its users to do more. More Karma equals more privileges on the site.
- Pre-search: Once you begin typing your question, Stack Overflow’s pre-search will do a quick search to see whether the question has been asked before and display the result for easy access and to prevent duplication issues.
- Google is UI: Stack Overflow was built around the assumption that people will go to Google which will send them to the right page. Each URL has the name of the question; each URL is permanent and clean, Metatags, sitemaps; anything and everything was done to ensure Stack Overflow’s pages looked “reasonable to search engines.”
- Performance: Ensuring answers are provided super fast was imperative. As a result, Stack Overflow is built on a Microsoft stack. “This entire site is serving 16 million pages a month and we’re doing it off of two servers which are almost completely unloaded,” said Spolsky. One server is a Web server, the other is running Microsoft SQL Server 2008 and both are 8 core Xeon’s. While many may assume using an open source stack would be more efficient, Spolsky explained that while SQL Server licenses cost $5000 per box, the Microsoft stack is paying for itself in terms of reduced hardware.
- Critical Mass: It’s imperative to have critical mass on day one; to ensure people are available to answer questions. “That was one of the reasons I asked Jeff Attwood to be involved in the site,” Spolsky explained. Between Joel on Software (Spolsky’s blog) and Coding Horror (Attwood’s blog), the two had a combined visitor count of 1.3 million visitors per month. Combined with the weekly podcast the two began, they were certain to get at least 20-30 thousand programmers interested.