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
Looking back at my own Q&A How can I build a string from smaller pieces?, the answer is incredibly long. I'm essentially showing five different ways to solve the problem - because they all exis...
#2: Post edited
by
Karl Knechtel
·
2023-09-05T21:09:18Z (8 months ago)
Should self-answered Q&A use separate answers for different techniques/approaches?
- Should self-answered Q&A use separate answers for different techniques/approaches (even if there's a caveat that applies overall)?
#1: Initial revision
by
Karl Knechtel
·
2023-09-05T21:07:47Z (8 months ago)
Should self-answered Q&A use separate answers for different techniques/approaches?
Looking back at my own Q&A [How can I build a string from smaller pieces?](https://software.codidact.com/posts/289251/), the answer is incredibly long. I'm essentially showing five different ways to solve the problem - because they all exist, and well-informed developers should know about all of them. Would it make more sense to split the content up and make a separate answer for each? On the one hand, that would probably be a lot more digestible - I wouldn't feel the same compulsion to use details/summary tags to shrink everything in (nesting such tags feels deceptive to me, in a way). It would also allow others to comment on each approach separately, offer reactions etc. On the other hand, I don't want to come across as trying to farm votes (even if I certainly think that some ways to solve the problem are better than others, and separate scores from the community might better reflect that reality). More importantly, I wouldn't know what to do with the warning at the top of the answer - since it applies to a consideration of the overall problem, rather than the techniques used to solve it. If I continue adding the sort of content here that I plan on doing, I can only see this problem repeating itself; so I want to get a general sense of the best way to deal with these situations. Should I: * Leave the question and answer as is, and wait until we've come to a resolution on an article-type category etc. before trying to do more content like this? * Split the answer in five and move the warning into the question? * Split the answer in five and copy-paste the warning to each answer? * Split the question in six, somehow hammering the warning into the shape of a separate answer? * Something else?