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

60%
+1 −0
Meta Etiquette for posting comments

Before posting this on the help pages, I will compile the feedback in a separate answer. Generally speaking, comments should be helpful feedback and the following are not exhaustive lists. Can in...

posted 3y ago by Alexei‭

Answer
#1: Initial revision by user avatar Alexei‭ · 2021-05-05T06:54:20Z (over 3 years ago)
Before posting this on the help pages, I will compile the feedback in a separate answer.

Generally speaking, comments should be helpful feedback and the following are not exhaustive lists.

### Can include

- asking for question clarification. Examples: "what was the output of line X?", "can you include the stack trace?", "can you provide a reference for the second paragraph?"
- explaining why a different question might actually be what the poster is looking for
- explaining how the poster can find a solution (e.g. what search terms to try)
- explaining why the question is in violation of site rules
- explaining other reasons why the question is poorly received (receiving downvotes or got closed) and what to do to improve it
- +1 or thank you notes, if they also provide a little bit of information. Example: +1. This also worked with version X of the framework Y.

### Should be avoided

- lengthy digressive discussions (should be moved to a separate question)
- +1 or -1 with no explanation
- snarky comments. Example: "Codidact is not your personal assistant". Such comments can be easily replaced with clearer ones. Example: "Have you searched for X?". If the question shows no effort or it is very poor, you can downvote or flag for closure. 
- references to overall author activity in the community. If you feel a user's activity is an issue, please use flagging instead of comments.
- providing full answers in the comments (they should be added as answers)
- lengthy digressive discussions (should be moved to a separate question)