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 »
Meta

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Post History

66%
+2 −0
Meta Do we want a wiki (or similar) alongside Q&A?

There are a few ways to understand "wiki". Like wikipedia - an interlinked web of articles in a standardized format. Like SO's documentation project or Github wikis - a stripped down wiki that ...

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

Answer
#2: Post edited by user avatar matthewsnyder‭ · 2023-08-08T17:00:16Z (over 1 year ago)
  • There are a few ways to understand "wiki".
  • 1. Like wikipedia - an interlinked web of articles in a standardized format.
  • 2. Like SO's documentation project or Github wikis - a stripped down wiki that is kind of sort of like a wiki but also weirdly shallow.
  • 3. A post without answers, where the post itself is the point.
  • 4. Question that does not have a single right answer, but is open ended, every answer is one possible item, which the community votes up or down, and the "true" answer is the ranked list of all answers.
  • 1 is a clear no - wiki sites are too different. If the CD team wants to try a separate wiki project, I would excitedly follow it, but I think mixing the two would be like oil and water.
  • 2 - I don't have much experience with. I remember when SO tried it, as an observer it seemed neat and interesting, but disappeared out of nowhere. I would love to hear a detailed retrospective from someone who used it heavily - but I think it's more complicated than CD needs to be. Again, as a separate project, might be great, but it's at cross purposes with CD's simple Q&A format.
  • 3 - This is an interesting one, I guess https://proposals.codidact.com/ is this model too. What I like is that it's a nice, logical extension of the Q&A principle. What's weird to me is that it feel very restrictive to have only comments, not answers, to elaborate on the question. But that restriction goes away once you realize you can just ask questions in the other category and link to it. So perhaps this is something that feels new and scary, but as people get used to it over time, will become a much appreciated aspect of Q&A sites.
  • 4 - This was the DIY way on SO to do "wikis". The recipes example on pre-2010 SO would have been "what are the best desert recipes?", with each answer a different recipe (sometimes alternates of the same). Soon after 2010 SO decided these were no longer okay, and I can sort of see the argument about open-ended, never resolved, etc. But if it was up to me I'd use it. Notably, this format survived on some niche sites, like code golf (especially the `popularity-contest` tag), where it seems to be working quite well.
  • I feel like the ideal solution would be something like 3 or 4. But instead of "questions without answers" it would be "answers without a question". The difference being that people can post multiple *alternate* version of the same thing, and let the best one win. For example, I posted https://proposals.codidact.com/posts/288625 - but maybe someone feels it's all a bunch of crap and they want to completely rewrite it. It's a bit hard to do that with edits sometimes, because edits are not as exposed to community consensus and dialogue. But if they could post an "answer" to my "question" which is basically the same post, but rewritten to be better (according to them), I think that would be the best solution. Recipes are another great example of this - it's certainly valuable to be able to post a few alternative takes on veggie stuffed peppers. And it's not a matter of "the best recipe" - often it's nice to have a few variants, and it's not about eliminating all but the best.
  • **tl;dr:** The articles are nice, but they are too biased towards the OP's take on the subject. We should allow posting alternate versions of articles as "answers" to them.
  • There are a few ways to understand "wiki".
  • 1. Like wikipedia - an interlinked web of articles in a standardized format.
  • 2. Like SO's documentation project or Github wikis - a stripped down wiki that is kind of sort of like a wiki but also weirdly shallow.
  • 3. A post without answers, where the post itself is the point.
  • 4. Question that does not have a single right answer, but is open ended, every answer is one possible item, which the community votes up or down, and the "true" answer is the ranked list of all answers.
  • 1 is a clear no - wiki sites are too different. If the CD team wants to try a separate wiki project, I would excitedly follow it, but I think mixing the two would be like oil and water.
  • 2 - I don't have much experience with. I remember when SO tried it, as an observer it seemed neat and interesting, but disappeared out of nowhere. I would love to hear a detailed retrospective from someone who used it heavily - but I think it's more complicated than CD needs to be. Again, as a separate project, might be great, but it's at cross purposes with CD's simple Q&A format.
  • 3 - This is an interesting one, I guess https://proposals.codidact.com/ is this model too. What I like is that it's a nice, logical extension of the Q&A principle. What's weird to me is that it feel very restrictive to have only comments, not answers, to elaborate on the question. But that restriction goes away once you realize you can just ask questions in the other category and link to it. So perhaps this is something that feels new and scary, but as people get used to it over time, will become a much appreciated aspect of Q&A sites.
  • 4 - This was the DIY way on SO to do "wikis". The recipes example on pre-2010 SO would have been "what are the best dessert recipes?", with each answer a different recipe (sometimes alternates of the same). Soon after 2010 SO decided these were no longer okay, and I can sort of see the argument about open-ended, never resolved, etc. But if it was up to me I'd use it. Notably, this format survived on some niche sites, like code golf (especially the `popularity-contest` tag), where it seems to be working quite well.
  • I feel like the ideal solution would be something like 3 or 4. But instead of "questions without answers" it would be "answers without a question". The difference being that people can post multiple *alternate* version of the same thing, and let the best one win. For example, I posted https://proposals.codidact.com/posts/288625 - but maybe someone feels it's all a bunch of crap and they want to completely rewrite it. It's a bit hard to do that with edits sometimes, because edits are not as exposed to community consensus and dialogue. But if they could post an "answer" to my "question" which is basically the same post, but rewritten to be better (according to them), I think that would be the best solution. Recipes are another great example of this - it's certainly valuable to be able to post a few alternative takes on veggie stuffed peppers. And it's not a matter of "the best recipe" - often it's nice to have a few variants, and it's not about eliminating all but the best.
  • **tl;dr:** The articles are nice, but they are too biased towards the OP's take on the subject. We should allow posting alternate versions of articles as "answers" to them.
#1: Initial revision by user avatar matthewsnyder‭ · 2023-06-23T01:44:13Z (over 1 year ago)
There are a few ways to understand "wiki".

1. Like wikipedia - an interlinked web of articles in a standardized format.
2. Like SO's documentation project or Github wikis - a stripped down wiki that is kind of sort of like a wiki but also weirdly shallow.
3. A post without answers, where the post itself is the point.
4. Question that does not have a single right answer, but is open ended, every answer is one possible item, which the community votes up or down, and the "true" answer is the ranked list of all answers.

1 is a clear no - wiki sites are too different. If the CD team wants to try a separate wiki project, I would excitedly follow it, but I think mixing the two would be like oil and water.

2 - I don't have much experience with. I remember when SO tried it, as an observer it seemed neat and interesting, but disappeared out of nowhere. I would love to hear a detailed retrospective from someone who used it heavily - but I think it's more complicated than CD needs to be. Again, as a separate project, might be great, but it's at cross purposes with CD's simple Q&A format.

3 - This is an interesting one, I guess https://proposals.codidact.com/ is this model too. What I like is that it's a nice, logical extension of the Q&A principle. What's weird to me is that it feel very restrictive to have only comments, not answers, to elaborate on the question. But that restriction goes away once you realize you can just ask questions in the other category and link to it. So perhaps this is something that feels new and scary, but as people get used to it over time, will become a much appreciated aspect of Q&A sites.

4 - This was the DIY way on SO to do "wikis". The recipes example on pre-2010 SO would have been "what are the best desert recipes?", with each answer a different recipe (sometimes alternates of the same). Soon after 2010 SO decided these were no longer okay, and I can sort of see the argument about open-ended, never resolved, etc. But if it was up to me I'd use it. Notably, this format survived on some niche sites, like code golf (especially the `popularity-contest` tag), where it seems to be working quite well.

I feel like the ideal solution would be something like 3 or 4. But instead of "questions without answers" it would be "answers without a question". The difference being that people can post multiple *alternate* version of the same thing, and let the best one win. For example, I posted https://proposals.codidact.com/posts/288625 - but maybe someone feels it's all a bunch of crap and they want to completely rewrite it. It's a bit hard to do that with edits sometimes, because edits are not as exposed to community consensus and dialogue. But if they could post an "answer" to my "question" which is basically the same post, but rewritten to be better (according to them), I think that would be the best solution. Recipes are another great example of this - it's certainly valuable to be able to post a few alternative takes on veggie stuffed peppers. And it's not a matter of "the best recipe" - often it's nice to have a few variants, and it's not about eliminating all but the best.

**tl;dr:** The articles are nice, but they are too biased towards the OP's take on the subject. We should allow posting alternate versions of articles as "answers" to them.