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 Do we need more specific up/down vote reasons for Software Development community?
Post
Do we need more specific up/down vote reasons for Software Development community?
The help center includes a rather generic (it's the same for all communities) article about voting.
Recently a user flagged a question asking why it had received so many downvotes. While flagging is not for this type of issue, this made me wonder if users are aware of how upvote and downvote are supposed to work and what they mean for Software Development community.
Should we have a more clear and concise way of conveying the information about upvoting and downvoting?
As a reference, I like how SE network shows concise tooltips for each of the two actions:
For questions
- Upvote - This question shows research effort; it is useful and clear
- Downvote - This question does not show any research effort; it is unclear of not useful
For answers
- Upvote - this answer is useful
- Downvote - this answer is not useful
Not sure how it would be better from a UX perspective, but replacing the computed score with such tooltips might provide more value.
1 comment thread