Timeline for For an iterative review, is it okay to edit my own question to include revised code?

7 events

when toggle format	what		by	license	comment
Apr 13, 2017 at 12:41	history	edited	CommunityBot		replaced http://codereview.stackexchange.com/ with https://codereview.stackexchange.com/
Jul 5, 2014 at 6:55	comment	added	Mark Ross		Yes, but by sticking to the original code only, then the only real way to show progress is to post new questions for each iteration. This seems 'unwieldy' at best. Why not allow an area for the 'current working code' in addition to the original question. I do agree that the original question should remain untouched. But, as it is, there doesn't seem to be a good way to show progress within a question and that's a shame. Btw, the 'current working code' shouldn't count toward the poster's standing.
Jun 16, 2014 at 6:11	history	made wiki			Post Made Community Wiki by JamalMod
Apr 15, 2014 at 10:41	history	edited	konijn	CC BY-SA 3.0	added 1 characters in body
Apr 14, 2014 at 20:39	history	edited	konijn	CC BY-SA 3.0	added 74 characters in body
Apr 14, 2014 at 20:29	comment	added	Jamal Mod		It would still be problematic to have new answers on updated code in the same question. If two or three updates is not enough, there may be a fourth. It can become very confusing very fast. By sticking to just the original code, there's a more direct link between the review and the code.
Apr 14, 2014 at 20:27	history	answered	konijn	CC BY-SA 3.0