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

42%
+1 −2
Q&A A refactoring convenience function.

Here is a redraft and elaboration of what this post is about, partially in response to some comments I've received. This post may be about a few different things at once, and may need to be refact...

2 answers  ·  posted 10mo ago by Julius H.‭  ·  edited 9mo ago by Julius H.‭

#4: Post edited by user avatar Julius H.‭ · 2024-02-12T19:01:24Z (9 months ago)
  • _Here is a redraft and elaboration of what this post is about, partially in response to some comments I've received._
  • _This post may be about a few different things at once, and may need to be refactored. (In my opinion, this makes it interesting as a question, since the post acts as a demonstration of what the question is itself about.)_
  • **Some sub-topics here:**
  • 1. A refactoring convenience function.
  • 2. In general, to what extent is the design intention of Codidact discourage unnecessary on-platform edits?
  • 3. What is a "braindump" (in this context), and to what extent is it against the design intention of Codidact?
  • ### **1. A refactoring convenience function.**
  • This is a simple topic and I would like to migrate it to a separate question, when I have some time. I just mean a button that reduces the number of mouse clicks, for when you believe a post should be separated into multiple separate questions. It occurs often on Stack Exchange that a question is closed as containing multiple questions. I have often had the thought, "Why not make it easy to split it apart into its constituent questions, then?"
  • ### **2. In general, to what extent is the design intention of Codidact to discourage unnecessary on-platform edits?**
  • I am new here, so I don't know who has the most influence or personal ownership of "what the purpose of Codidact is". I originally thought it was Monica Cellio, but now think user Andreas also plays a huge role. I am not here to tell anyone what the purpose is, only to suggest ideas to help realize its purpose, once I understand it more fully.
  • I would like clarification regarding if it is a priority of this platform that people try relatively hard to meticulously prepare good-quality posts off of the platform, before posting them. If that is an explicit intention, then I can think of ways that the site moderation can facilitate that and realize that goal. On the other hand, what is the *final* purpose of discouraging, say, sloppy contributions? During my time on Stack Exchange, I never minded editing and refining other people's posts. I found it fun. On Stack Exchange, edits on a question do indeed "bump them up" in the feed. That was never a problem for me. One commenter seems to suggest that it is not good for there to be too many active edits on a question. Can anyone confirm this part of the Codidact aim?
  • ### **3. What is a "braindump" (in this context), and to what extent is it against the design intention of Codidact?**
  • I will migrate this sub-question to another post soon, but it touches, again, on my understand of the aim of Codidact. To be expanded later.
  • _Here is a redraft and elaboration of what this post is about, partially in response to some comments I've received._
  • _This post may be about a few different things at once, and may need to be refactored. (In my opinion, this makes it interesting as a question, since the post acts as a demonstration of what the question is itself about.)_
  • **Some sub-topics here:**
  • 1. A refactoring convenience function.
  • 2. In general, to what extent is the design intention of Codidact discourage unnecessary on-platform edits?
  • 3. What is a "braindump" (in this context), and to what extent is it against the design intention of Codidact?
  • ### **1. A refactoring convenience function.**
  • This is a simple topic and I would like to migrate it to a separate question, when I have some time. I just mean a button that reduces the number of mouse clicks, for when you believe a post should be separated into multiple separate questions. It occurs often on Stack Exchange that a question is closed as containing multiple questions. I have often had the thought, "Why not make it easy to split it apart into its constituent questions, then?"
  • ### **2. In general, to what extent is the design intention of Codidact to discourage unnecessary on-platform edits?**
  • I am new here, so I don't know who has the most influence or personal ownership of "what the purpose of Codidact is". I originally thought it was Monica Cellio, but now think user Andreas also plays a huge role. I am not here to tell anyone what the purpose is, only to suggest ideas to help realize its purpose, once I understand it more fully.
  • I would like clarification regarding if it is a priority of this platform that people try relatively hard to meticulously prepare good-quality posts off of the platform, before posting them. If that is an explicit intention, then I can think of ways that the site moderation can facilitate that and realize that goal. On the other hand, what is the *final* purpose of discouraging, say, sloppy contributions? During my time on Stack Exchange, I never minded editing and refining other people's posts. I found it fun. On Stack Exchange, edits on a question do indeed "bump them up" in the feed. That was never a problem for me. One commenter seems to suggest that it is not good for there to be too many active edits on a question. Can anyone confirm this part of the Codidact aim?
  • ### **3. What is a "braindump" (in this context), and to what extent is it against the design intention of Codidact?**
  • I will migrate this sub-question to another post soon, but it touches, again, on my understanding of the aim of Codidact. To be expanded later.
#3: Post edited by user avatar Julius H.‭ · 2024-02-12T19:01:05Z (9 months ago)
  • _Here is a redraft and elaboration of what this post is about, partially in response to some comments I've received._
  • _This post may be about a few different things at once, and may need to be refactored. (In my opinion, this makes it interesting as a question, since the post acts as a demonstration of what the question is itself about.)_
  • **Some sub-topics here:**
  • 1. A refactoring convenience function.
  • 2. In general, to what extent is the design intention of Codidact discourage unnecessary on-platform edits?
  • 3. What is a "braindump" (in this context), and to what extent is it against the design intention of Codidact?
  • ### **1. A refactoring convenience function.**
  • This is a simple topic and I would like to migrate it to a separate question, when I have some time. I just mean a button that reduces the number of mouse clicks, for when you believe a post should be separated into multiple separate questions. It occurs often on Stack Exchange that a question is closed as containing multiple questions. I have often had the thought, "Why not make it easy to split it apart into its constituent questions, then?"
  • ### **2. In general, to what extent is the design intention of Codidact to discourage unnecessary on-platform edits?**
  • I am new here, so I don't know who has the most influence or personal ownership of "what the purpose of Codidact is". I originally thought it was Monica Cellio, but now think user Andreas also plays a huge role. I am not here to tell anyone what the purpose is, only to suggest ideas to help realize its purpose, once I understand it more fully.
  • I would like clarification regarding if it is a priority of this platform that people try relatively hard to meticulously prepare good-quality posts off of the platform, before posting them. If that is an explicit intention, then I can think of ways that the site moderation can facilitate that and realize that goal. On the other hand, what is the *final* purpose of discouraging, say, sloppy contributions? During my time on Stack Exchange, I never minded editing and refining other people's posts. I found it fun. On Stack Exchange, edits on a question do indeed "bump them up" in the feed. That was never a problem for me. One commenter seems to suggest that it is not good for there to be too many active edits on a question. If this part of the Codidact aim?
  • ### **3. What is a "braindump" (in this context), and to what extent is it against the design intention of Codidact?**
  • I will migrate this sub-question to another post soon, but it touches, again, on my understand of the aim of Codidact. To be expanded later.
  • _Here is a redraft and elaboration of what this post is about, partially in response to some comments I've received._
  • _This post may be about a few different things at once, and may need to be refactored. (In my opinion, this makes it interesting as a question, since the post acts as a demonstration of what the question is itself about.)_
  • **Some sub-topics here:**
  • 1. A refactoring convenience function.
  • 2. In general, to what extent is the design intention of Codidact discourage unnecessary on-platform edits?
  • 3. What is a "braindump" (in this context), and to what extent is it against the design intention of Codidact?
  • ### **1. A refactoring convenience function.**
  • This is a simple topic and I would like to migrate it to a separate question, when I have some time. I just mean a button that reduces the number of mouse clicks, for when you believe a post should be separated into multiple separate questions. It occurs often on Stack Exchange that a question is closed as containing multiple questions. I have often had the thought, "Why not make it easy to split it apart into its constituent questions, then?"
  • ### **2. In general, to what extent is the design intention of Codidact to discourage unnecessary on-platform edits?**
  • I am new here, so I don't know who has the most influence or personal ownership of "what the purpose of Codidact is". I originally thought it was Monica Cellio, but now think user Andreas also plays a huge role. I am not here to tell anyone what the purpose is, only to suggest ideas to help realize its purpose, once I understand it more fully.
  • I would like clarification regarding if it is a priority of this platform that people try relatively hard to meticulously prepare good-quality posts off of the platform, before posting them. If that is an explicit intention, then I can think of ways that the site moderation can facilitate that and realize that goal. On the other hand, what is the *final* purpose of discouraging, say, sloppy contributions? During my time on Stack Exchange, I never minded editing and refining other people's posts. I found it fun. On Stack Exchange, edits on a question do indeed "bump them up" in the feed. That was never a problem for me. One commenter seems to suggest that it is not good for there to be too many active edits on a question. Can anyone confirm this part of the Codidact aim?
  • ### **3. What is a "braindump" (in this context), and to what extent is it against the design intention of Codidact?**
  • I will migrate this sub-question to another post soon, but it touches, again, on my understand of the aim of Codidact. To be expanded later.
#2: Post edited by user avatar Julius H.‭ · 2024-02-12T18:59:12Z (9 months ago)
tried to clarify and separate into separated questions.
  • A new way to enable the desire to “brain-dump”?
  • A refactoring convenience function.
  • One long-standing thing I’ve experienced on SE is sometimes you honestly have a ton of questions or thoughts you want to get out of your head, posted. But in principle being limited to one question per post, and sometimes one post per 40 minutes, sometimes feels counterproductively slow, even squeezing.
  • Could there be a novel solution to this pain point?
  • What if it was more common for contributors to convert a long multipart question into separate question posts, afterwards? Then you could brain-dump, then you or others later refine and structure. Maybe there could even be a “split” function - you press it and two side by side text fields pop up to help separate the question into multiple question posts - then post them all at once?
  • _Here is a redraft and elaboration of what this post is about, partially in response to some comments I've received._
  • _This post may be about a few different things at once, and may need to be refactored. (In my opinion, this makes it interesting as a question, since the post acts as a demonstration of what the question is itself about.)_
  • **Some sub-topics here:**
  • 1. A refactoring convenience function.
  • 2. In general, to what extent is the design intention of Codidact discourage unnecessary on-platform edits?
  • 3. What is a "braindump" (in this context), and to what extent is it against the design intention of Codidact?
  • ### **1. A refactoring convenience function.**
  • This is a simple topic and I would like to migrate it to a separate question, when I have some time. I just mean a button that reduces the number of mouse clicks, for when you believe a post should be separated into multiple separate questions. It occurs often on Stack Exchange that a question is closed as containing multiple questions. I have often had the thought, "Why not make it easy to split it apart into its constituent questions, then?"
  • ### **2. In general, to what extent is the design intention of Codidact to discourage unnecessary on-platform edits?**
  • I am new here, so I don't know who has the most influence or personal ownership of "what the purpose of Codidact is". I originally thought it was Monica Cellio, but now think user Andreas also plays a huge role. I am not here to tell anyone what the purpose is, only to suggest ideas to help realize its purpose, once I understand it more fully.
  • I would like clarification regarding if it is a priority of this platform that people try relatively hard to meticulously prepare good-quality posts off of the platform, before posting them. If that is an explicit intention, then I can think of ways that the site moderation can facilitate that and realize that goal. On the other hand, what is the *final* purpose of discouraging, say, sloppy contributions? During my time on Stack Exchange, I never minded editing and refining other people's posts. I found it fun. On Stack Exchange, edits on a question do indeed "bump them up" in the feed. That was never a problem for me. One commenter seems to suggest that it is not good for there to be too many active edits on a question. If this part of the Codidact aim?
  • ### **3. What is a "braindump" (in this context), and to what extent is it against the design intention of Codidact?**
  • I will migrate this sub-question to another post soon, but it touches, again, on my understand of the aim of Codidact. To be expanded later.
#1: Initial revision by user avatar Julius H.‭ · 2024-02-10T05:20:30Z (10 months ago)
A new way to enable the desire to “brain-dump”?
One long-standing thing I’ve experienced on SE is sometimes you honestly have a ton of questions or thoughts you want to get out of your head, posted. But in principle being limited to one question per post, and sometimes one post per 40 minutes, sometimes feels counterproductively slow, even squeezing.

Could there be a novel solution to this pain point?

What if it was more common for contributors to convert a long multipart question into separate question posts, afterwards? Then you could brain-dump, then you or others later refine and structure. Maybe there could even be a “split” function - you press it and two side by side text fields pop up to help separate the question into multiple question posts - then post them all at once?