11

Existing rules These are covered in multiple questions Question body: Should a post with no specific question(s) imply a general review? Should [programming-challenge] questions require a summary of the challenge? Reviewing design: Should design questions be on-topic here? Reviewing "design" If there is little/no code: Can I ask a question ...


7

If there were a mechanism (?) to impose an edit freeze while discussion happens, I'd vote for that, but I don't know that there is one. Actually... there is a mechanism for that. It's just not available to regular users. For cases where edits keep getting applied back and forth, diamond moderators have the ability to lock a post. Before this happens it can ...


3

Users that are new to the network may not intuitively understand that they do not own any of the content they post on Stack Exchange, as per terms of service all user content is licensed under CC-BY-SA, and as content hosted on the SE network it is the duty of network users to make sure all network content looks great and reads well, and this is incentivized ...


3

Code that's not included can not be reviewed. That's simple. "I don't want to separate it into independent questions because the components altogether form the whole architecture; I think that the entire context is important here." Considering you've posted the general overview and context in your first question, that question can serve as extra ...


2

I think there are multiple levels of issues / reviews. Character level review. These are the 'petty' points such as style guide conformance and whitespace issues. You should have spaces on both sides of operators. Line level review. These are normally pretty basic changes and focus on how to improve the readability of a specific line. It's more Pythonic ...


Only top voted, non community-wiki answers of a minimum length are eligible