0
\$\begingroup\$

This question already has an answer here:

It it acceptable to ask questions that have arisen from another answer, repeatedly.

For example...

  1. I post working code and ask to have it reviewed.

  2. Someone answers with some suggestions.

  3. I re-write the code, and as it is so different from the original code, I post if for review as a separate question.

  4. Then, because I have not fully understood the suggestions as they are perhaps quite general, someone offers some more advice to better structure the code.

This keeps going on and on until eventually there is a whole load of questions that all build on each other and I have a well structured solution that relied very heavily on the Code Review Q&A site.

\$\endgroup\$

marked as duplicate by 200_success discussion Aug 16 '17 at 18:04

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

  • 2
    \$\begingroup\$ IMO you're walking on the fence with design questions - we review working, implemented code, not hypothetical, high-level designs. "The code is the design": we review design when the code we see is organized in such a way that properly addressing code issues implies revisiting the whole design, e.g. a WPF application where OP would have implemented everything in the code-behind - reviews are very likely to direct the OP towards a MVVM pattern, for example. Can you clarify what you mean with "questions about a design in your head"? These would be off-topic. \$\endgroup\$ – Mathieu Guindon Aug 16 '17 at 14:16
  • \$\begingroup\$ I have re-written the question \$\endgroup\$ – user3755946 Aug 16 '17 at 15:20
  • 2
    \$\begingroup\$ Do How to post a follow-up question? and Is code ever clean enough? - Can there be too many follow-up questions? answer your question? \$\endgroup\$ – Mathieu Guindon Aug 16 '17 at 15:23

Browse other questions tagged .