7
\$\begingroup\$

I posted a question for Code Review, and other than a few comments, what I was told was that I should put actual code of the process and people were only interested in knowing that. What I really wanted was a review on design, not the implementation detail. But it was downvoted and trail of comments asking me to put actual code. Am I missing something here?

\$\endgroup\$
  • 5
    \$\begingroup\$ What I really wanted was a review on design, not the implementation detail. That's your problem right there friend. We want your implementation detail. That's really the whole purpose of this site. We help you to improve the implementation of the design you've settled on and specified. \$\endgroup\$ – RubberDuck Sep 4 '15 at 14:03
15
\$\begingroup\$

I'm the moderator that cleaned up the 25-or-so comments on your post, and reopened your question after the // do something placeholders were replaced with actual code.

Thank you for coming to meta.

Am I missing something here?

Yes.

Please read why is hypothetical code off-topic?, which goes into the details of why the site's regulars voted to close your question and demanded to edit the actual code into the post.

About the design, see reviewing "design", which explains how the design is the code; we review code, not design; asking a boiled-down question stripped of its context and specifically looking for a "design review" is outside our scope. However when you post your actual code, and the design is wrong, it's more than likely that a reviewer will point it out - asking for a design review is off-topic, but answering can cover any and all aspects of the code, and that includes the design.

\$\endgroup\$

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .