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

60%
+1 −0
Q&A How should we approach a programming site or sites?

I don't know about eventually, but while codidact is still getting started, it's better to not splinter communities. Critical mass is make or break for communities. Getting to that critical mass i...

posted 1y ago by matthewsnyder‭  ·  edited 1y ago by matthewsnyder‭

Answer
#3: Post edited by user avatar matthewsnyder‭ · 2023-06-09T22:02:59Z (over 1 year ago)
  • I don't know about *eventually*, but while codidact is still getting started, it's better to not splinter communities.
  • Critical mass is make or break for communities. Getting to that critical mass is the most vital objective by far, early on. Reaching critical mass for one community is obviously easier than reaching it for 5 communities at once, that cannibalize engagement between each other. This does not apply to completely orthogonal communities though - software vs. Christianity has a lot less cannibalization than "professional" software vs... I guess amateur software? It will be the same people going to both anyhow.
  • Note, it's critical mass of questions too, not just users. So even if every user codidact diligently frequents all sections, their energy is still split between many sites. It's better to lump things together as much as possible. Ideally, communities should only be split if both daughter communities will still have critical mass.
  • This was one of the mistakes of SX. Instead of starting general and splitting off popular generic tags as needed, which would result in exponential growth, they insist that new communities be started in Area 51 from scratch, meaning that the critical mass problem must be solved again and again. It's like building a moon base and still launching all your rockets from Earth.
  • I've been active on SO, programmers, code review and a few other related sites. I feel like the boundary was always kind of thin. Based what I've seen, the most parsimonious explanation for why some of these offshoots exist was a combination of elitism, users being annoyed that not every question caters to them, and creating rules for the sake of rules on the older and more general sections. A lot of these offshoots could have just been tags that people can hide or favorite as they like. I suppose it does allow you to sequester moderation scope of users a bit, which is harder with tags. But then what is the value of locking a programmers out of moderating SO?
  • But this is really a discussion for the future. Right now the few programming sections are floundering. User count and activity are precious, and splitting sections would halve them or worse. For now it should definitely be handled by tags.
  • I don't know about *eventually*, but while codidact is still getting started, it's better to not splinter communities.
  • Critical mass is make or break for communities. Getting to that critical mass is the most vital objective by far, early on. Reaching critical mass for one community is obviously easier than reaching it for 5 communities at once, that cannibalize engagement between each other. This does not apply to completely orthogonal communities though - software vs. Christianity has a lot less cannibalization than "professional" software vs... I guess amateur software? It will be the same people going to both anyhow.
  • Note, it's critical mass of questions too, not just users. So even if every user codidact diligently frequents all sections, their energy is still split between many sites. It's better to lump things together as much as possible. Ideally, communities should only be split if both daughter communities will still have critical mass.
  • This was one of the mistakes of SX. Instead of starting general and splitting off popular generic tags as needed, which would result in exponential growth, they insist that new communities be started in Area 51 from scratch, meaning that the critical mass problem must be solved again and again. It's like building a moon base and still launching all your rockets from Earth.
  • I've been active on SO, programmers, code review and a few other related sites. I feel like the boundary was always kind of thin. Based what I've seen, the most parsimonious explanation for why some of these offshoots exist was a combination of elitism, users being annoyed that not every question caters to them, and creating rules for the sake of rules on the older and more general sections. A lot of these offshoots could have just been tags that people can hide or favorite as they like. I suppose it does allow you to sequester moderation scope of users a bit, which is harder with tags. But then what is the value of locking a programmers mod out of moderating SO?
  • But this is really a discussion for the future. Right now the few programming sections are floundering. User count and activity are precious, and splitting sections would halve them or worse. For now it should definitely be handled by tags.
#2: Post edited by user avatar matthewsnyder‭ · 2023-06-09T22:02:37Z (over 1 year ago)
  • I don't know about *eventually*, but while codidact is still getting started, it's better to not splinter communities.
  • Critical mass is make or break for communities. Getting to that critical mass is the most vital objective by far, early on. Reaching critical mass for one community is obviously easier than reaching it for 5 communities at once, that cannibalize engagement between each other. This does not apply to completely orthogonal communities though - software vs. Christianity has a lot less cannibalization than "professional" software vs... I guess amateur software? It will be the same people going to both anyhow.
  • Note, it's critical mass of questions too, not just users. So even if every user codidact diligently frequents all sections, their energy is still split between many sites. It's better to lump things together as much as possible. Ideally, communities should only be split if both daughter communities will still have critical mass.
  • This was one of the mistakes of SX. Instead of starting general and splitting off popular generic tags as needed, which would result in exponential growth, they insist that new communities be started in Area 51 from scratch, meaning that the critical mass problem must be solved again and again.
  • I've been active on SO, programmers, code review and a few other related sites. I feel like the boundary was always kind of thin. Based what I've seen, the most parsimonious explanation for why some of these offshoots exist was a combination of elitism, users being annoyed that not every question caters to them, and creating rules for the sake of rules on the older and more general sections. A lot of these offshoots could have just been tag that people can hide or favorite as they like. I suppose it does allow you to sequester moderation scope of users a bit, which is harder with tags. But then what is the value of locking a programmers out of moderating SO?
  • But this is really a discussion for the future. Right now the few programming sections are floundering. User count and activity are precious, and splitting sections would halve them or worse. For now it should definitely be handled by tags.
  • I don't know about *eventually*, but while codidact is still getting started, it's better to not splinter communities.
  • Critical mass is make or break for communities. Getting to that critical mass is the most vital objective by far, early on. Reaching critical mass for one community is obviously easier than reaching it for 5 communities at once, that cannibalize engagement between each other. This does not apply to completely orthogonal communities though - software vs. Christianity has a lot less cannibalization than "professional" software vs... I guess amateur software? It will be the same people going to both anyhow.
  • Note, it's critical mass of questions too, not just users. So even if every user codidact diligently frequents all sections, their energy is still split between many sites. It's better to lump things together as much as possible. Ideally, communities should only be split if both daughter communities will still have critical mass.
  • This was one of the mistakes of SX. Instead of starting general and splitting off popular generic tags as needed, which would result in exponential growth, they insist that new communities be started in Area 51 from scratch, meaning that the critical mass problem must be solved again and again. It's like building a moon base and still launching all your rockets from Earth.
  • I've been active on SO, programmers, code review and a few other related sites. I feel like the boundary was always kind of thin. Based what I've seen, the most parsimonious explanation for why some of these offshoots exist was a combination of elitism, users being annoyed that not every question caters to them, and creating rules for the sake of rules on the older and more general sections. A lot of these offshoots could have just been tags that people can hide or favorite as they like. I suppose it does allow you to sequester moderation scope of users a bit, which is harder with tags. But then what is the value of locking a programmers out of moderating SO?
  • But this is really a discussion for the future. Right now the few programming sections are floundering. User count and activity are precious, and splitting sections would halve them or worse. For now it should definitely be handled by tags.
#1: Initial revision by user avatar matthewsnyder‭ · 2023-06-09T21:01:08Z (over 1 year ago)
I don't know about *eventually*, but while codidact is still getting started, it's better to not splinter communities.

Critical mass is make or break for communities. Getting to that critical mass is the most vital objective by far, early on. Reaching critical mass for one community is obviously easier than reaching it for 5 communities at once, that cannibalize engagement between each other. This does not apply to completely orthogonal communities though - software vs. Christianity has a lot less cannibalization than "professional" software vs... I guess amateur software? It will be the same people going to both anyhow.

Note, it's critical mass of questions too, not just users. So even if every user codidact diligently frequents all sections, their energy is still split between many sites. It's better to lump things together as much as possible. Ideally, communities should only be split if both daughter communities will still have critical mass.

This was one of the mistakes of SX. Instead of starting general and splitting off popular generic tags as needed, which would result in exponential growth, they insist that new communities be started in Area 51 from scratch, meaning that the critical mass problem must be solved again and again.

I've been active on SO, programmers, code review and a few other related sites. I feel like the boundary was always kind of thin. Based what I've seen, the most parsimonious explanation for why some of these offshoots exist was a combination of elitism, users being annoyed that not every question caters to them, and creating rules for the sake of rules on the older and more general sections. A lot of these offshoots could have just been tag that people can hide or favorite as they like. I suppose it does allow you to sequester moderation scope of users a bit, which is harder with tags. But then what is the value of locking a programmers out of moderating SO?

But this is really a discussion for the future. Right now the few programming sections are floundering. User count and activity are precious, and splitting sections would halve them or worse. For now it should definitely be handled by tags.