How do we define duplicate questions?
In other stackexchange sites, questions like:
What is the use of Models in MVC? Why should we use Models in MVC?
may be closed down since they are so alike. However, in Code Review - questions like:
Please review my response class. Please review my response class.
might not be duplicate at all, since they might be posting different classes. It might be similar, it might be very different, and no matter how similar both code is, if there is a difference, then it's not the same code and the answers for one might not apply to the other.
How do you gauge whether or not is it a duplicate in Code Review? I wanted to post my class in code review for comments, but I am afraid of getting voted down.
Thanks for the sites.
After reading for a while, I think I kinda get it. If my code is similar to the one already posted, I should just post the differences.
But I still think Code Review is quite different from other stack exchange site and should probably have rules that differs a bit. I still can't pinpoint the problem is, and example is this, when I try to create a question titled
First try in Response class, let me know what you think., this comes up:
"The question you are asking appears to be subjective and is likely to be closed."
It's not a wording problem, since I tried
What do you think of my response class? and it's rebuked too. I think this is ridiculous. Code Review is a site to ask for peer reviews right? Why am I not allowed to ask for other people's opinions (criticisms, feedback) on the class I just wrote? Or am I misunderstanding Code Review?
The way I see is, Code Review isn't a Q/A site like stack overflow or stack exchange is. In a Q/A site, you ask when you have a problem. In a site for peer-reviewing like Code Exchange, you don't have a problem. You just want to get some feedback, criticisms, suggestions, and learn from them. In fact, if you already identified a problem, you wouldn't post it in Code Review, you would've tried to solve it, or asked about it in stackoverflow.com. It's because you don't know what problem your code might have that you want it to be peer-reviewed. This is why, I think, Code Review is not a Q/A site, and therefore, cannot be effectively managed with the same rules as other stackexchange sites.