Why StackExchange Will Eventually Fail(weblogs.asp.net)
weblogs.asp.net
Why StackExchange Will Eventually Fail
http://weblogs.asp.net/rosherove/archive/2010/09/24/why-stackexchange-will-eventually-fail-control-freak-ism.aspx
5 comments
Please change the title of this post. The article has nothing to do with why (or whether) Stack Exchange will fail. It could be more aptly titled "What I dislike about Stack Exchange".
From the article:
> my answers are my own, and they reflect my mood, and my typos. and if they want me ot fix them they should ask me.
'Mood' is useless to those reading your posts, regardless of whether you care. I like SO because the answers are for the community and not individual egos.
> my answers are my own, and they reflect my mood, and my typos. and if they want me ot fix them they should ask me.
'Mood' is useless to those reading your posts, regardless of whether you care. I like SO because the answers are for the community and not individual egos.
I actually like edits on my questions/answers because they are usually always an improvement to what I wrote.
No reason as to actually WHY StackExchange will fail is given, but rather it's a whining about the StackExchange sites approval mechanism. I may agree with the author and may dislike this mechanism too, but the article has nothing to do with the title and is very emotional.
My thoughts exactly. I actually like the fact that users can edit questions and answers. This, plus the voting mechanism ensures the best information is present in most cases.
The intention of this post is to be polarizing and controversial in order garner traffic. It doesn't deliver on anything insightful or interesting.
I find it quite interesting. It overviews the history of the StackExchange program and expresses how the rules for the program are quite arbitrary and that Jeff and Joel are the ultimate gatekeepers.
It's posts like these that often allow those running the ship to get objective feedback on how their decisions are affecting the community.
It came across a little nasty, but informative nonetheless.
It's posts like these that often allow those running the ship to get objective feedback on how their decisions are affecting the community.
It came across a little nasty, but informative nonetheless.
Things such as community websites almost always "fail". Esp from the perspective of early adopters. At time passes and things grow they change, their "goals" change, their "community" changes. These changes are often seen as failures of the original "vision" believed to have existed by each "generation" of users.
But, yelling fail from asp.net is hilarious as ASP is almost guaranteed to fail when MS needs some revenue or market leverage and gets everyone to dump ASP/.net dev stack for MS's latest "greatest" acronym.
But, yelling fail from asp.net is hilarious as ASP is almost guaranteed to fail when MS needs some revenue or market leverage and gets everyone to dump ASP/.net dev stack for MS's latest "greatest" acronym.