Hacker News new | ask | show | jobs
by AtticusTheGreat 3359 days ago
This is exactly my stance on the matter. Don't litter the code with unnecessary comments that will never get acted upon. Instead, make a story in your bug tracker and act upon it.
2 comments

The reason TODOs have survived the test of time is that bug trackers come and go while source code sticks around.
Not only that, but bugs come and go. People add a bunch of tech debt issues into the system, then a bunch of feature requests, possible bugs, and whatnot gets added. Then some big milestone or release comes up and everyone filters through the list, deciding what to fix and what not to. And then anything that doesn't need to get fixed "RIGHT GODDAMN NOW" often ends up on the ash heap of history, never to be seen again. And then years later someone looks at the code or runs into a bug and remembers "oh yeah..., hey, we should fix this eventually".

If you want to fix/change something eventually at some indeterminate time in the future then comment TODOs are a good place for that sort of issue to live.

It seems the TODOs are not the problem but the fact that they are not acted on.