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.

Comments on Should asking about book recommendations directly connected to software development be on-topic?

Parent

Should asking about book recommendations directly connected to software development be on-topic?

+11
−0

Context

We have recently received a suggestion to allow questions about recommending books directly connected to software development.

The way I see this now (pros and cons)

Pros:

  • allow more questions that help software developers

Cons:

  • tend to be open-ended, unless there is not a vast domain (e.g. Java development)
  • tend to be opinion based

What do you think? Should we allow such questions?

History

0 comment threads

Post
+3
−0

I would argue that book recommendations might fit into "Software documentation" or, considering books a technology in and of themselves, "Software development tools."

The policy does not appear to have been updated one way or another. In the intervening three years, the web has gotten filled with more slop. Search has been degraded to the point of being pretty much useless and many people (self included) want to hang out in communities that are not Reddit, Hacker News, or some random Discord. Being able to discuss the (typically) high quality information found in books would be helpful.

A tag could be encouraged. I see some folks objecting to the Q&A nature. Perhaps there may be a room for, as others have suggested, a separate category for the community? Perhaps, it could be something like "Discussions." You would then need to determine what is on and off topic for that and manage all the tags as well, but it would keep such questions out of the Q&A feed.

History

1 comment thread

Maintenance & expertise (2 comments)
Maintenance & expertise
Lundin‭ wrote 7 months ago

As written in my old answer in this thread, formalizing rules for how to handle recommendations lists is necessary. But for the list to also become good with actual lasting value, you also need access to numerous domain experts about a particular topic, who in addition to their expertise have also read a lot of books about it. If you leave recommendations open to anyone, then it won't be a quality list of books but just a list of random books, recommended by random people. And that's the problem: to track down enough experts would require a large user base. I don't think we can do this with any programming language currently.

Monica Cellio‭ wrote 7 months ago

One possibility could be to use a discussions/recommendations/etc category to collect information, and then have a knowledgable person distill it down into a canonical question or article in the Q&A section. The discussion remains available for those who want to keep discussing, and the canonical version gets the visibility of the Q&A category.