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

Dashboard
Notifications
Mark all as read
Meta

Should we have a Code Review Section / category?

+9
−0

As discussed on Meta, should Software.codidact allow reviewing working code as a question?

Traffic is probably not high enough to warrant it's own Codereview community. The existing communities out there for reviewing code are not well known. New users may even view this as a new idea & it differentiates software.codidact from other software communities.

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

3 answers

You are accessing this answer with a direct link, so it's being shown above all other answers regardless of its score. You can return to the normal view.

+6
−0

I would definitely allow code review questions (requests) as they are an important part of any professional software developer.

A special category might make sense, although a designated special tag (code-review) might be enough if it also results in a special highlight for at least for the tag.

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

1 comment thread

General comments (5 comments)
+7
−0

I agree and I think it should be a separate category, with separate posting rules. There are several examples of how the rules for each category would likely be fundamentally different:

Main Q&A category

  1. Encourages minimal examples to reproduce the problem, particularly when asking for debug help.
  2. It is fine to post questions seeking help to fix code which isn't working.
  3. Allows theoretical or big picture questions such as algorithm theory or program design.
  4. Can ask what code written by others does/works.

Code review category

  1. Encourages posting the complete code as-is, with no modifications.
  2. All code must be compiled and tested, with no known bugs.
  3. Must contain code.
  4. The poster should be the author of the code and describe what it does as part of the question.
Why does this post require moderator attention?
You might want to add some details to your flag.

1 comment thread

General comments (4 comments)
+6
−0

Proposal, based on the feedback here so far: because code-review questions have special rules, create a category. This allows (and we would need proposed text from the community for):

  • Category description: that short text at the top of the posts list; can contain links.

  • Posting guidance: you know that text you see about the first textbox when you click on "ask question"? That text can be fully customized. Summarize the rules for code-review posts (like that the code must already work). If it requires more explanation than fits reasonably in that block, summarize there and add a help topic.

  • (Optional) help topic, per the previous bullet. Or not.

  • (Optional) any changes/additions to close reasons that you need to support this. We can't do per-category close reasons, but we can include the scope in the reasons at least.

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

0 comment threads

Sign up to answer this question »