Skip to main content
Commonmark migration
Source Link

##Our Solution

Our Solution

##Our Solution

Our Solution

deleted 3 characters in body
Source Link
Robert Cartaino
  • 111.4k
  • 35
  • 232
  • 406

There's a big difference between defining a site and using a site. Asking questions and expecting answers (and providing answers) is using the site. I don't want to create "Google bait" with half-assed questions dumped into what may turn out to be an ill-defined idea. That goes against everything that makes these sites great. Quality and correctness matter! So we have to add in ALL those tools and behaviors which vet the value of the information now available to on the Internet.

There's a big difference between defining a site and using a site. Asking questions and expecting answers (and providing answers) is using the site. I don't want to create "Google bait" with half-assed questions dumped into what may turn out to be an ill-defined idea. That goes against everything that makes these sites great. Quality and correctness matter! So we have to add in ALL those tools and behaviors which vet the value of the information now available to on the Internet.

There's a big difference between defining a site and using a site. Asking questions and expecting answers (and providing answers) is using the site. I don't want to create "Google bait" with half-assed questions dumped into what may turn out to be an ill-defined idea. That goes against everything that makes these sites great. Quality and correctness matter! So we have to add in ALL those tools and behaviors which vet the value of the information now available on the Internet.

added 27 characters in body; added 2 characters in body
Source Link
Robert Cartaino
  • 111.4k
  • 35
  • 232
  • 406

Good-bye Area 51; In spirit, itIt would no longer exist, in spirit. We'd simply be creating Stack Exchange sites based on the mere suggestion that a topic might be a good idea. "Wouldn't it be cool to have a site about [X]?" *Poof* Done. That sounds like the failed model of Stack Exchange 1.0.

But let's say we can overcome the "trial site" problem. What if the proposal did not work out? Would we foldsimply delete it?

There are two major problems with this approach:

(1) Users are incensed when we throw away "content." Can you imagine if we let people spend months (or longer) contributing hundreds (maybe thousands) of questions and poured their knowledge into answering them… then, if the "proposal" doesn't work out, we just delete all that content?

Remember the first days of Area 51? We found that people were using the voting very differently from how we intended. So we discarded three days of voting data. That led to weeks of protests from users claiming to be demotivated, angered at losing all that effort, tired of us wasting their time, etc, etc; All that for discarding three days of voting… three days.

(2) The site develops momentum before it is even defined. People would simply start asking questions before the site had any boundaries. That run-away momentum would preclude being able to set those boundaries. Ill-conceived questions would attract more of the same. After all, what would preclude others asking similar questions (your "Google bait") when they see the same type of questions on the site? What are people voting on? The quality of the question? The appropriateness for the site? Whether it is a good on- or off-topic question? That subtle distinction would be lost on the vast majority of users.

  1. Users are incensed when we throw away "content." Can you imagine if we let people spend months (or longer) contributing hundreds (maybe thousands) of questions and poured their knowledge into answering them… then, if the "proposal" doesn't work out, we just delete all that content?

    Remember the first days of Area 51? We found that people were using the voting very differently from how we intended. So we discarded three days of voting data. That led to weeks of protests from users claiming to be demotivated, angered at losing all that effort, tired of us wasting their time, etc, etc; All that for discarding three days of voting… three days.

  2. The site develops momentum before it is even defined. People would simply start asking questions before the site had any boundaries. That run-away momentum would preclude being able to set those boundaries. Ill-conceived questions would attract more of the same. After all, what would preclude others asking similar questions (your "Google bait") when they see the same type of questions on the site? What are people voting on? The quality of the question? The appropriateness for the site? Whether it is a good on- or off-topic question? That subtle distinction would be lost on the vast majority of users.

Good-bye Area 51; In spirit, it would no longer exist. We'd simply be creating Stack Exchange sites based on the mere suggestion that a topic might be a good idea. "Wouldn't it be cool to have a site about [X]?" *Poof* Done. That sounds like the failed model of Stack Exchange 1.0.

But let's say we can overcome the "trial site" problem. What if the proposal did not work out? Would we fold it?

There are two major problems with this approach:

(1) Users are incensed when we throw away "content." Can you imagine if we let people spend months (or longer) contributing hundreds (maybe thousands) of questions and poured their knowledge into answering them… then, if the "proposal" doesn't work out, we just delete all that content?

Remember the first days of Area 51? We found that people were using the voting very differently from how we intended. So we discarded three days of voting data. That led to weeks of protests from users claiming to be demotivated, angered at losing all that effort, tired of us wasting their time, etc, etc; All that for discarding three days of voting… three days.

(2) The site develops momentum before it is even defined. People would simply start asking questions before the site had any boundaries. That run-away momentum would preclude being able to set those boundaries. Ill-conceived questions would attract more of the same. After all, what would preclude others asking similar questions (your "Google bait") when they see the same type of questions on the site? What are people voting on? The quality of the question? The appropriateness for the site? Whether it is a good on- or off-topic question? That subtle distinction would be lost on the vast majority of users.

Good-bye Area 51; It would no longer exist, in spirit. We'd simply be creating Stack Exchange sites based on the mere suggestion that a topic might be a good idea. "Wouldn't it be cool to have a site about [X]?" *Poof* Done. That sounds like the failed model of Stack Exchange 1.0.

But let's say we can overcome the "trial site" problem. What if the proposal did not work out? Would we simply delete it?

There are two major problems with this approach:

  1. Users are incensed when we throw away "content." Can you imagine if we let people spend months (or longer) contributing hundreds (maybe thousands) of questions and poured their knowledge into answering them… then, if the "proposal" doesn't work out, we just delete all that content?

    Remember the first days of Area 51? We found that people were using the voting very differently from how we intended. So we discarded three days of voting data. That led to weeks of protests from users claiming to be demotivated, angered at losing all that effort, tired of us wasting their time, etc, etc; All that for discarding three days of voting… three days.

  2. The site develops momentum before it is even defined. People would simply start asking questions before the site had any boundaries. That run-away momentum would preclude being able to set those boundaries. Ill-conceived questions would attract more of the same. After all, what would preclude others asking similar questions (your "Google bait") when they see the same type of questions on the site? What are people voting on? The quality of the question? The appropriateness for the site? Whether it is a good on- or off-topic question? That subtle distinction would be lost on the vast majority of users.

deleted 54 characters in body
Source Link
Robert Cartaino
  • 111.4k
  • 35
  • 232
  • 406
Loading
added 108 characters in body; added 11 characters in body; added 1 characters in body
Source Link
Robert Cartaino
  • 111.4k
  • 35
  • 232
  • 406
Loading
Source Link
Robert Cartaino
  • 111.4k
  • 35
  • 232
  • 406
Loading