Number 1 and Number 11 seem to be contradicting each other, but I suppose you could interpret #1 as saying “Don’t just say ‘I’ll fix it later’, but write it down.”
Whenever I encounter a situation like this, or a feature improvement that would be good in this spot, I always write a TODO, which is what #1 is saying. You need to keep track of these things or they’ll get lost.
Also, when on teams, I try to promote the format # TODO(sfz-): thing to do 2017-04-25 so that if someone has time to pick any up, they know who to contact for details or whether the issue might be stale or irrelevant.
# TODO(sfz-): thing to do 2017-04-25
The problem with that is people sometimes leave the organization. A slightly better version is to include an ID for your issue-tracking system that has more details.