TODO doesn’t mean you actually intend to do something. It’s a marker for the next person that the logic was left unfinished and they shouldn’t be surprised by missing corner cases or strange code structure.
// TODO(never): ...
Will it motivate the next person to fix it? Of course not. TODO is an admission that the current code is good enough for practical purposes. If it weren’t you would have fixed it.
Wow this blew up. Check out my soundcloud justjavascript.com
This also means keeping code “clean” of TODOs is a terrible idea. You’re not actually completing your software, you’re just hiding the fact it’s incomplete from the reader.
Some Senior developers say: Dan, you’re giving bad advice to Junior developers and now they do all these bad things in our codebases. My answer to this is: yes, and thank you
Don’t let the Clean Code Cult eat you
A bit more nuanced
