Skip to main content
8 events
when toggle format what by license comment
Jun 15, 2020 at 8:20 history edited CommunityBot
Commonmark migration
Sep 29, 2010 at 9:22 comment added MikeSchinkel Mod @Jan Fabry: One of the problems is the SO architecture simply doesn't support scale well for questions or for people. For the latter Joel & Jeff seem to want to deny the community aspect by trying to limit conversations (even though they build reputation systems.) The problem with the current SO architecture is that both questions and users get lost in a sea of too many unrelated questions and too many unrelated users. I can't easily see on SO who are the experts for a given tag and I can't close off and create a sandbox if I want to. The tag system just isn't sufficient.
Sep 29, 2010 at 9:09 comment added MikeSchinkel Mod @Jan Fabry: See: shirky.com/writings/group_enemy.html "The downside of going for size and scale above all else is that the dense, interconnected pattern that drives group conversation and collaboration isn't supportable at any large scale. Less is different -- small groups of people can engage in kinds of interaction that large groups can't. ... Larger than a dozen, smaller than a few hundred, where people can actually have these conversational forms that can't be supported when you're talking about tens of thousands or millions of users, at least in a single group"
Sep 29, 2010 at 9:08 comment added MikeSchinkel Mod @Jan Fabry - What SE probably needs to do is merge ALL sites into one and at the same time improve their architecture so that it can still feel like we have separate sights. The community could choose to promote a tag to be a category/site at a subdomain of SE and that subdomain filters for questions and users by those tagged with the site's category. It wouldn't be trivial but I don't see how they are ever going to solve this problem of two little, too big unless they merge them all together or unless they quit pushing the idea that all site must be large.
Sep 29, 2010 at 9:03 comment added MikeSchinkel Mod @Jan Fabry - In my experience it also increases the chance that you'll get an inappropriate answer. I saw many WordPress questions on SO where the person answering showed how to write a SQL query when the preferred way among WordPress developers is to use the query API. On SO you've got people jumping on questions they are not qualified to answer. And since the person asking doesn't know any better they mark the bad answer as correct. That's one of many reasons why I prefer smaller more focused sites like WordPress Answers.
Sep 29, 2010 at 7:41 comment added Jan Fabry On the main Stack Overflow site, I usually just browse unanswered questions in the [wordpress] tag, and have an RSS feed for the [propel] tag. But I really like the fact that there is overlap: if I ask a question about database issues in WordPress, it is very well possible that someone who likes MySQL but not WordPress could also answer it. This increases the chance that I get an answer. To achieve the same effect if there was both a MySQL and a WordPress site, I would have to duplicate the question on both sites.
Sep 29, 2010 at 0:30 history edited MikeSchinkelMod CC BY-SA 2.5
Added UPDATE
Sep 28, 2010 at 23:02 history answered MikeSchinkelMod CC BY-SA 2.5