12
\$\begingroup\$

I'm referring to this question specifically. The OP knows the code as-is doesn't work and is looking for the answer to a specific question.

\$\endgroup\$
18
\$\begingroup\$

IMO fixing broken code should be off-topic here.

To be properly reviewed, code should at least pass basic tests, hopefully pass lint, pre-commit hooks and a full test run without known bugs or automated warnings (that'd be a waste of time for everyone involved).

Given the nature of the site, we are bound to meet "HELPMYCODEISBROKEN". I suggest we strictly move those to SO, but this is the easy part.

What happens with "this works, but is there a better way to..."? This could (I believe would) be on topic here, but if the line could be drawn at "coder is done picking options and ready to commit" we'd have an easier time figuring out whether to move stuff.

\$\endgroup\$
  • 3
    \$\begingroup\$ um, I assume by "OT" you mean off-topic and not on-topic? \$\endgroup\$ – BenV Jan 19 '11 at 23:40
  • 4
    \$\begingroup\$ The site to me is about Improving code, whilst sharing technique, and not fixing errors. +1 \$\endgroup\$ – RobertPitt Jan 19 '11 at 23:42
  • 2
    \$\begingroup\$ +1 I agree with what's been said here. If we start trying to figure out why someone else's piece of code doesn't work then it shifts the focus from improving the code to debugging the code which isn't what this SE is about. So I'd say such questions would fit better in SO. \$\endgroup\$ – greatwolf Jan 20 '11 at 0:01
  • \$\begingroup\$ +1 for the first sentence. +many more if I could for the rest of the answer \$\endgroup\$ – LRE Jan 20 '11 at 0:10
  • \$\begingroup\$ created a discussion similar to this: meta.codereview.stackexchange.com/questions/52/… please add your thoughts. \$\endgroup\$ – cbrulak Jan 20 '11 at 0:55

You must log in to answer this question.

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