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

81%
+7 −0
Meta To transfer, or not to, that is the question: whether 'tis nobler to let it stay or to take arms against Stack Overflow's dominance of FAQ canonicals

Hi and welcome to the site. :) I think the idea of a canonical like the one you linked is great. A lot of newbies have too little understanding of their topic to identify common patterns. So they ...

posted 1y ago by matthewsnyder‭

Answer
#1: Initial revision by user avatar matthewsnyder‭ · 2023-07-20T02:06:27Z (over 1 year ago)
Hi and welcome to the site. :)

I think the idea of a canonical like the one you linked is great. A lot of newbies have too little understanding of their topic to identify common patterns. So they keep asking many trivial variations of the same handful of basic questions. People with even intermediate knowledge of the topic will usually have learned how to connect their instance of a problem to the general form and go from there, but of course everyone starts as a newbie. Because newbies cannot properly connect their problem to the big picture, it is useful and better for everyone to connect it with the big picture for them. I posted [some](https://software.codidact.com/posts/280965) [thoughts](https://linux.codidact.com/posts/288309) along these lines here, but I did a worse job than you because I did not provide a good, concrete example. Your question is exactly the type of thing I was thinking of.

For https://stackoverflow.com/questions/62336082 in particular, I think the main issue there is that it's quite long. I think it would be better to create a separate question for each error (like `How do I debug "cannot convert some value to data type" errors?`) and then simply link to them from the main debugging question. This doesn't change any of the content, just reorganizes it and makes it easier to skim.

IMO this content would be very valuable for several reasons:

* It is useful and well written
* It solves a real problem
* It's about an interesting and non-trivial technology