Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Codidact Meta!

Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.

Post History

80%
+6 −0
Q&A What's more important for codidact - quality or helping questions get answered?

Codidact started as an attempt to make something better/different than SE. When it was started, pretty much everyone involved shared a consensus about what it should not be: Not run by a private...

posted 8mo ago by Lundin‭  ·  edited 8mo ago by Michael‭

Answer
#2: Post edited by user avatar Michael‭ · 2024-03-25T16:51:44Z (8 months ago)
Make the list into a table. A couple grammar things.
  • Codidact started as an attempt to make something better/different than SE. When it was started, pretty much everyone involved shared a consensus about what it should _not_ be:
  • - Not run by a private company for profit, where the agenda suddenly changes at a whim depending on what buzzword that's fashionable for the moment.
  • - Not a place where representatives from a private company keeps saying one thing and then doing something else.
  • - Not something with closed source where which features to develop next were chosen by a selected few.
  • And so on. With everyone perfectly in agreement about what the site _should not_ be, it is easy to make the assumption that everyone will also be in agreement about what the site _should_ be. I remember the early forum we had set up, wildly brain-storming about literally everything. The ambitions were high, but also all over the place.
  • At that point, everyone gathers up their own personal but diverse experiences from SE and assumes that the site would be exactly as they personally envisioned it. Including often contradicting opinions like:
  • - SE is rude/unwelcoming/elitist. We should make something more welcoming and friendly.
  • - SE is drowning in low quality content. We should make something of higher quality here, in order to attract the subject matter experts and to increase search engine rankings.
  • - SE is narrow-minded about what topics to discuss. We should make something with broader scope and tolerance to more subjective topics.
  • - SE is drowning in beginner-level FAQ repeated over and over again. The so-called "canonical duplicates" are of diverse quality and we could do better.
  • Personally, I've probably been pushing for all of these at some point, but they admittedly risk clashing with each in several ways. Another user might have one single thing they consider the most important of all and are propagating for that one. Not necessarily the same thing as yet another user. The end result will be a mix - a community consensus of what every user participating think is important. Individual users may have to compromise, but that is how the world works whenever dealing with humans co-existing in groups.
  • So I think what Codidact boils down to is _community-driven_. Not all sites under the Codidact umbrella need to have the same emphasis of what's important for that particular community.
  • For example, something like a Code Golf community probably needs to have a very strict scope/format/rules and with emphasis on quality. Whereas something like a Philosophy site would probably benefit from being more tolerant to broad and subjective topics.
  • So the way to go is probably to raise a local discussion per community over what the preferences and scope should be locally. And it's a never-ending discussion, as new users join and should have their say.
  • Codidact started as an attempt to make something better/different than SE. When it was started, pretty much everyone involved shared a consensus about what it should _not_ be:
  • - Not run by a private company for profit where the agenda suddenly changes at a whim, depending on which buzzword is fashionable for the moment.
  • - Not a place where representatives from a private company keep saying one thing and then doing something else.
  • - Not something with closed source where the features to develop next were chosen by a selected few.
  • And so on. With everyone perfectly in agreement about what the site _should not_ be, it is easy to make the assumption that everyone will also be in agreement about what the site _should_ be. I remember the early forum we had set up, wildly brain-storming about literally everything. The ambitions were high, but also all over the place.
  • At that point, everyone gathers up their own personal but diverse experiences from SE and assumes that the site would be exactly as they personally envisioned it. Including often-contradictory opinions like:
  • | Problem | Solution|
  • |-|-|
  • | SE is rude/unwelcoming/elitist. | We should make something more welcoming and friendly.|
  • | SE is drowning in low quality content. | We should make something of higher quality here, in order to attract the subject matter experts and to increase search engine rankings. |
  • | SE is narrow-minded about what topics to discuss. | We should make something with broader scope and tolerance to more subjective topics. |
  • | SE is drowning in beginner-level FAQ repeated over and over again. | The so-called "canonical duplicates" are of diverse quality and we could do better. |
  • Personally, I've probably been pushing for all of these at some point, but they admittedly risk clashing with each other in several ways. Another user might have one single thing they consider the most important of all and are pushing for that one, which isn't necessarily the same thing as yet another user. The end result will be a mix&mdash;a community consensus of what every user participating thinks is important. Individual users may have to compromise, but that is how the world works whenever dealing with humans co-existing in groups.
  • So I think what Codidact boils down to is _community-driven_. Not all sites under the Codidact umbrella need to have the same emphasis of what's important for that particular community.
  • For example, something like a Code Golf community probably needs to have a very strict scope/format/rules and with emphasis on quality. Whereas something like a Philosophy site would probably benefit from being more tolerant to broad and subjective topics.
  • So the way to go is probably to raise a local discussion per community over what the preferences and scope should be locally. And it's a never-ending discussion, as new users join and should have their say.
#1: Initial revision by user avatar Lundin‭ · 2024-03-25T14:28:27Z (8 months ago)
Codidact started as an attempt to make something better/different than SE. When it was started, pretty much everyone involved shared a consensus about what it should _not_ be: 

- Not run by a private company for profit, where the agenda suddenly changes at a whim depending on what buzzword that's fashionable for the moment. 
- Not a place where representatives from a private company keeps saying one thing and then doing something else. 
- Not something with closed source where which features to develop next were chosen by a selected few.

And so on. With everyone perfectly in agreement about what the site _should not_ be, it is easy to make the assumption that everyone will also be in agreement about what the site _should_ be. I remember the early forum we had set up, wildly brain-storming about literally everything. The ambitions were high, but also all over the place.

At that point, everyone gathers up their own personal but diverse experiences from SE and assumes that the site would be exactly as they personally envisioned it. Including often contradicting opinions like:

- SE is rude/unwelcoming/elitist. We should make something more welcoming and friendly.
- SE is drowning in low quality content. We should make something of higher quality here, in order to attract the subject matter experts and to increase search engine rankings.
- SE is narrow-minded about what topics to discuss. We should make something with broader scope and tolerance to more subjective topics.
- SE is drowning in beginner-level FAQ repeated over and over again. The so-called "canonical duplicates" are of diverse quality and we could do better.

Personally, I've probably been pushing for all of these at some point, but they admittedly risk clashing with each in several ways. Another user might have one single thing they consider the most important of all and are propagating for that one. Not necessarily the same thing as yet another user. The end result will be a mix - a community consensus of what every user participating think is important. Individual users may have to compromise, but that is how the world works whenever dealing with humans co-existing in groups.

So I think what Codidact boils down to is _community-driven_. Not all sites under the Codidact umbrella need to have the same emphasis of what's important for that particular community. 

For example, something like a Code Golf community probably needs to have a very strict scope/format/rules and with emphasis on quality. Whereas something like a Philosophy site would probably benefit from being more tolerant to broad and subjective topics. 

So the way to go is probably to raise a local discussion per community over what the preferences and scope should be locally. And it's a never-ending discussion, as new users join and should have their say.