Skip to main content

StackOverflow


I've spent the last couple of weeks hanging out on StackOverflow, and thinking about how successful its design is.

Incase you haven't heard of it, StackOverflow is a question-and-answer site for programmers, put together by two popular programming bloggers, Joel Spolsky and Jeff Atwood. Participants get given 'reputation points' when their questions or answers are voted-up by other people. This makes the site very useful because when you ask a question there are loads of programmers online practically falling over each other to answer your question. I guess programmers all like to get positive feedback from their peers, and thats what the vote system provides.

The reputation system is just one design point out of several that Joel and Jeff obviously thought very carfully about when building the site. A few weeks ago Joel gave a googletech talk about StackOverflow, going into detail about how they designed it:



He makes the interesting point in this video that Human-Computer interaction is now quite well understood, and that Human-to-Human interaction on the web is a more challenging area now. As in the real world, the environment affects people's behaviour, and so the UI choices made on a website will greatly influence how people use the site.

He says that Microsoft estimate that there are about 9 million professional programmers in the world, and as of April 2009 StackOverflow is getting about 3 million distinct visitors a month. So just 6 months after launch they have 33% of their total possible audience in attendance.

Towards the end of the talk he also has some interesting observations on why the StackOvervlow approach might not translate well to non-technical domains. He says
"I dont think this site is going to work for gardening questions, ever". For example, because they could take a certain amount of technical know-how for granted in their userbase, they were able to make great use of features like tagging without having to explain it to anyone.

The video is about an hour long but worth watching if you want some insight into the design of a great site.

My username on StackOverflow is codeulike, and today I achieved the little milestone of 1,000 reputation points, which also inspired me to make this post ; )

Comments

Popular posts from this blog

Copying data to Salesforce Sandboxes using TalenD

A common problem with Salesforce Developer Sandboxes is that they are blank. Really you're going to want some data in there, so there are various strategies for copying data from your live instance to the Sandbox. There are some paid-for solutions - SFXOrgData , Salesforce Partial Data Sandboxes - but if you've got a decent ETL tool you can build your own. There are a bunch of free ETL tools for Salesforce: JitterBit Data Loader is good for quick ad-hoc tasks but the free version makes it difficult to manage specific ETL projects or share projects with other users Pentaho Community Edition - an open source edition of the enterprise version Apatar was a free open source Salesforce ETL which still works but development seems to have stopped since 2011 TalenD Open Studio is an open source ETL tool For the task of copying data from live to a Sandbox, either Pentaho or TalenD Open Studio could be used, depending on preference. Here's a good comparison of the dif

SSRS multi-value parameters with less fail

SSRS supports multi-value parameters, which is nice, but there are a few issues with them. This is how I deal with them. Two of the problems with SSRS multi-value parameters are: You have to jump through a few hoops to get them to work with stored procedures The (Select All) option, as shown above The reason the (Select All) option is a problem is that it is a really inelegant way of saying 'this parameter does not matter to me'. If you have a list with hundreds of values, passing all of them as a default option just seems wrong. Also, if your report shows the user which items they selected, printing the whole list when they choose (Select All) is excessive. So in this post I'm going to show my particular way of: Jumping through the hoops to get Multi-Value params in a stored procedure Adding a single '--All--' value that the report interprets as meaning all the options. Getting Multi-Value params to work with Stored Procedures This is

Remote Desktop on High DPI screens

Scott Hanselman wrote a nice blog post back in January about some of the issues you might face running Windows on a High DPI screen like that of a Surface Pro or Lenova Yoga. I'm kindof mystified that he didn't mention Remote Desktop though because thats been the number one problem for me on High DPI screens. That said, if you remote into very recent Server OS's like Windows Server 2012 R2, then apparently Remote Desktop will sort out the DPI scaling automatically. Perhaps Scott hadn't noticed the Remote Desktop issue because he only remotes into Server 2012 R2. Certainly if I was Scott, I wouldn't remote into anything less than that. But, in practice, I regularly have to remote into Server 2008 machines and yes even Server 2003. If you do that from a high DPI screen, the remote desktop is rendered at regular pixel size, which makes everything tiny. Its hard to show screenshots of High DPI screens that correctly convey the pixel size, so I've photoshoppe