I'm skeptical of use of TODO in general, because we rarely know what the future portends. To say "TODO" is to assert what must be done in the future, when in re

I'm skeptical of use of TODO in general, because we rarely know what the future portends. To say "TODO" is to assert what must be done in the future, when in reality all we can typically say is "NOTDOING". That said, "TODO" is well-understood by a lot of editors, so it's often useful to just drop that word in the source code to make it easier to find. A more reliable approach is to: 1. File a ticket, and 2. Leave a comment in the code linking to it: // This code does X, but it'd be better to do Y. At the time of writing // fixing this doesn't seem to be an issue worth fixing. // // See: https://bugtracker.example.com/... It's very difficult to write code that correctly predicts the future, but it's easy to write code that accurately describes the status quo at time of writing.