4 ms·
Your points are valid, and I've used it as well many times, but ther's always the risk you find yourself in a situation where there's just a growing number of T
by stinos 7y ago
Your points are valid, and I've used it as well many times, but ther's always the risk you find yourself in a situation where there's just a growing number of TODO items. Which isn't (always) a problem per se, but severely limits there usefulness and could be a sign of ever-expanding problems all over the code base. Worst I've seen is REALLYTODO popping up, then you know the ship is probably beyond sinking. Then again, in principle this is no different from growing todo lists, ever expanding issue tracker issues, ... But at least you can search those for context more easily imo.
- heavenlyblue 7y agoTo be fair, I believe many projects simply lack the second set of eyes which would downgrade those TODO to basic comments or along the lines of FUTURETODO
- dev_tty01 7y agoToo much typing. Try FUDO.
- heavenlyblue 7y agoThis is more of a bikeshedding question, but I’d go with NOTE instead.
- foobarian 7y agoOne of the more entertaining activities at work is to make fun of ancient TODO comments in our giant codebase. There are some all-stars most of us know by heart such that they made it into the internal company jargon. Tl;dr we ask to resolve TODOs during code review and don't allow them in now.