Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

9
  • 27
    Actually this IMO enforces poor questions like "I have a problem please help me, the code is below" - quite rarely code needs to be separated from the question. Best questions go like this "I want to achieve this and wrote these two lines of code, but the effect is the following, what's the problem" - there's very little code heavily interleaved with plain language. Commented Jun 28, 2011 at 12:50
  • 4
    Your root observation is correct but your diagnosis is still wrong: in fact, Jeff is trying to improve the user interface via this approach. Furthermore, the current UI has already gone through several cycles and while I don’t doubt that it could be improved (drastically), I doubt that this would help against lazy idiots. Neither would your proposed solution. @sharptooth has this covered. Commented Jun 28, 2011 at 15:24
  • 2
    I would +1 for thinking out the box but I disagree with the specific suggestion, since posting "supporting code" forces a question flow that may be unnatural. I have never just dumped in code at the bottom of my question. I almost always post an intro, the sample code, then the actual question. If you accept this premise that inline code is essential, then some type of formatting is required -- formatting which must be entered by the user or recommended by the system. And that's the exact thing that Jeff is asking about doing. Commented Jun 28, 2011 at 16:23
  • 1
    @Konrad: In addition to my above comment and in response to yours, I don't believe the Jeff is improving the UI by taking this path, but merely treating the symptoms of an underlying problem. If the UI was improved so that the mistake couldn't be made, then the solution of alerting the user would not be necessary. I am under no illusion that my example is the final solution but some thought needs to go into the question "are we presenting this in the best way possible?". Commented Jun 28, 2011 at 20:29
  • 1
    The simple sentence please mark code using the {} button around the text box could be enough. Commented Jun 28, 2011 at 23:55