After receiving some good feedback on my first question, I decided to edit my question to incorporate the advice with the idea to create a copy-pasteable "final version" for future visitors. However, I learned from comments that such edits are not recommended based on this Meta discussion.

It might be helpful to new users to explicitly mention that editing your question to address feedback is discouraged in the community tour.


A lot of things would be helpful to new users to explicitly mention in the tour... the whole entire Help Center would be helpful!

The thing about answer-invalidating edits isn't specific to Code Review in any way though: Stack Exchange being a Q&A concept (as opposed to a discussion forum concept), as described in the tour, rather implicitly implies that editing answered questions to turn them into impossible-to-follow discussions, is frowned upon.

The specific bit about answer-invalidating edits can be found on /help/someone-answers.

Except some site-specific images, the tour is essentially the same for all SE sites, as it's more about the mechanics of how Stack Exchange works, than it is about the site-specific rules you can find in the help center.

That said, mucho kudos for taking the tour!

  • \$\begingroup\$ I still think this should be explicitly mentioned in either How to Ask or the tour. Preferably in large font. Sure, it's somewhere in the help center, but do we really want to raise the entry barrier from "went through this quick, interesting-to-watch thing" to "read every single wall of text in the help center"? \$\endgroup\$ – Fund Monica's Lawsuit Nov 1 '17 at 16:00
  • 1
    \$\begingroup\$ @QPaysTaxes I get that, but if How to Ask becomes "everything you need to know about this site", it's no longer about "how to ask". \$\endgroup\$ – Mathieu Guindon Nov 1 '17 at 16:02
  • 1
    \$\begingroup\$ There's a difference between "everything you need to know about this site" and "the most important things to know about this site". One would be basically impossible to maintain; the other just includes the results of very important, non-intuitive things like, say, not updating the code. On SO it might be obvious, but on CR it seems to make sense that you'd update your code with the suggested fixes to get another round of reviews on it. It's important enough, and non-obvious enough, that it should be explicitly stated. \$\endgroup\$ – Fund Monica's Lawsuit Nov 1 '17 at 16:05

You must log in to answer this question.

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