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.

Comments on A refactoring convenience function.

Parent

A refactoring convenience function.

+1
−2

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.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

1 comment thread

Please don't edit your question in a way which invalidates existing answers (1 comment)
Post
+3
−2

If you want to evolve multiple questions from a long writeup, do it outside the site. There is nothing preventing you from writing as much text as you want as fast as you want into a file on your own system. Then, when you're ready, you can break up the brain dump into individual coherent posts. You don't need Codidact to solve that for you.

We don't want to see all the individual refinements on the way to a proper post. You wouldn't want to read a novel that changes every day as the author goes from a rough draft to the final version either.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

1 comment thread

Thank you for your response. The main reason I believe the general goal of having directly built-i... (5 comments)
Thank you for your response. The main reason I believe the general goal of having directly built-i...
Julius H.‭ wrote 10 months ago

Thank you for your response.

The main reason I believe the general goal of having directly built-in functions (such as buttons) for converting (or even “refactoring”) a single post into multiple separate posts is of value or interest is because of what you might call “user flow”: true, I could edit my posts meticulously before posting them. From a user perspective, would my experience of using the site be more or less identical, if I could refactor my posts with convenience functions within the site, vs. refactoring them outside, in a word processor? In my opinion, it would not, due to what I will call “user flow”. Arguably, even the mere fact that a certain button is accessible under a side-menu as opposed to directly visible on-screen at all times, changes the user experience of a software application - the mere fact that one must exert that tiny extra little 1 kJ of mental executive functioning, decision making, visual scanning, and clicking, in order to activate that function (…)

Julius H.‭ wrote 10 months ago · edited 10 months ago

changes how the user will feel using that function, how often they will choose to do so, etc.

I can go into more detail on this point of view. For now I wanted to say that to me, this is a functionality which would very much lend itself to what I currently understand a goal of Codidact to be - a system that encourages and facilitates that people edit posts for their longevity and readability as information resources. So to me, built-in refactoring functions could be as topical here as special video editing functions in a video editing software application. Sure, one can always say, “Well, you can just do it via the following alternative method, so that feature would therefore not be required.” I would say, the question is not if a feature is necessary, since the case can be made that virtually all software is ultimately unnecessary. The question is if it facilitates something that a user may find useful, I suppose. Personally, I would find it possibly useful.

Olin Lathrop‭ wrote 10 months ago

You're completely ignoring the point that we don't want to see all those edits. Activities like you suggest would have to bump those posts that were changed. That could drown out the new content that we do want to know about.

We don't want to dissipate volunteer energy on all those intermediate versions that aren't really ready to answer or otherwise worth spending time on. Maybe there is a slight convenience to you, but that is far outweighed by the annoyance to everyone else.

trichoplax‭ wrote 10 months ago

I agree this would be a distraction from questions that are already ready to answer.

There's something similar on Code Golf Codidact. The Sandbox category where people can post ideas for coding challenges and get feedback and slowly improve them until they are ready to post to the Challenges category. This is important for Code Golf because writing a clear, concise, unambiguous challenge specification is difficult. It seems far less important for questions, which are easier to write and less problematic to edit after they have been posted.

If we had this functionality at all I would definitely want it to be a separate category, rather than posting unfinished drafts in the main Q&A category. Any Codidact community can have a new category set up if there is community support for it on Meta. However, as far as I'm aware there is not yet functionality for a user to migrate a post from one category to another, so this may not meet your goal.

Julius H.‭ wrote 10 months ago

I think there is a misunderstanding that I was advocating a feature where you publicly post half-finished drafts of ideas to be collaborated and refined with others, as some sort of other category of post type. The core focus of my post is about built-in refactoring functions or buttons (or at least one). This applies to any question or answer, whether it was written hastily or not. The idea is to add a convenience function for the process of breaking a multipart question into separate question posts. You could do this for other people’s questions that you are moderating, not just your own. I am not saying that I insist we have this at all, just clarifying what the idea in my post is. It’s fine with me if people don’t want it.