### Tl;dr:  The minor improvements that takes an answer from 44 to 39 are often the most interesting and impressive feat. If you made the improvements, then you should post it as your answer.

---

I'll use [Luis Mendo][1]'s comments on one of my most [recent posts][2] as an example.

1. I posted my [original answer][3]
2. Luis Mendo commented and suggested a [**different** approach][3] that saved 5 bytes
3. I found [an approach][4] that saved another byte.
4. Luis found another [**different** approach][5] that saved 5 bytes
5. Before I even responded, Luis found **a _new_** [different approach][5] that saved yet another 9 bytes. 

Of course, there are similarities between the solutions, and they're probably based on the idea of the previous revisions, but it's still a different solution. Maybe Luis wouldn't have solved the challenge at all if it wasn't for my post<sup>1</sup>, but the shorter approaches are still his.

---

I suggest that:

- We still post comments suggesting simple improvements (_"you can use `1e3` instead of `1000`"_)
- We post _separate answers_, even if they're inspired by someone else's. And as always: Give credit where credit's due.

---

<sup>1 </sup>Of course he would, but let's pretend he wouldn't.  


  [1]: http://codegolf.stackexchange.com/users/36398/luis-mendo
  [2]: http://codegolf.stackexchange.com/a/112218/31516
  [3]: http://codegolf.stackexchange.com/revisions/112218/2
  [4]: http://codegolf.stackexchange.com/revisions/112218/4
  [5]: http://codegolf.stackexchange.com/questions/112208/charlie-oscar-delta-echo/112218#comment273454_112218