[p0nce]

A TODO means you have identified a way to make the code better. Since not everything needs to be at the highest quality, it is helpful to say what will benefit from being improved for future programmers.

If the TODO is not really "to do" before release, I change the name to: PERF (performance), MAYDO (nice to have) or FUTURE. If it doesn't break the user's story then it's not a real "to do".

I also leave comments for obvious good ideas that don't work, in case someone has the same idea later.

[t00]

TODOs are nicely indexed and collected by major IDE linters/code analyzers. Not sure if these alternatives are.