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?

+7
−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
Why does this post require moderator attention?
You might want to add some details to your flag.
Why should this post be closed?

0 comment threads

Post
+9
−0

I respect Alexei for opening a discussion on this, and Lundin for providing hard-won real world experience. I would like to put in a "pro", on the grounds that "I read this book and I'm a better programmer for it" is information that directly supports the codidact mission of helping each other learn. It's related to the old observation that bad IT people have walls full of certifications and good ones have shelves full of books. A fair question is how to maintain adequate quality and I'm short of concrete suggestions at the moment. Lundin's attempt to limit recommendations to things the person posting has actually read seems like a reasonable minimum.

History
Why does this post require moderator attention?
You might want to add some details to your flag.

1 comment thread

Beyond "I have read it and it was good" (1 comment)
Beyond "I have read it and it was good"
Lundin‭ wrote over 1 year ago

A quality list goes beyond "I have read it and it was good" though, because everyone can read a book and share an opinion of it. You can then get a recommendation about how easy to read and pedagogic the books was (similar to Amazon reviews perhaps). But not a measurement of technical correctness. Some aspects are more important when addressing beginners (you get away with simplifications) compared to when addressing veterans (everything said must be correct). What we wished SO to have was a list of book recommendations that had actually been read by domain experts who could also judge the technical correctness. Between myself and the domain expert who volunteered to maintain the list, we had maybe read ten or so of the books, less than half of what was listed at a whim. Better then if only books actually read by experts were listed and (anti) recommended after that.