[1980phipsi]

I think the key point is that if you put a TODO comment in the code, it should be resolved before merging. If it's important enough to leave in there, it should be an issue. I only use them as something to grep for and so that I don't lose my train of that as in "oh I need to fix that but I'm working on something else at the moment, write the TODO, finish what I'm working on, then go back to the TODO".

[hinkley]

If the todo is code you’re working on, yes.

If it’s a WTF about code that is next to the code you worked on, no. Boost the WTF ratio of code that deserves it.

[johnfn]

What if you're working on something, and you see some code that should be marked with TODO, entirely unrelated to your code? I think it's unrealistic to expect to be able to fix every issue you see.

[moi2388]

Then I create a ticket and we refine it to see if it indeed needs to be addressed

[RandallBrown]

This is how I use TODO as well. If it shows up in a pull request, it should be a red flag that the work isn't done.