5 ms·
#1 There's nothing wrong with TODO comments. Often you don't want implement feature B in full so that you can focus on feature A. Of course you've told your cus
by redcap 9y ago
#1 There's nothing wrong with TODO comments. Often you don't want implement feature B in full so that you can focus on feature A. Of course you've told your customers that you'll do both features, so you push feature B back to a future release. No problem in using TODO there - at least you have comments as to what's actually going on and what may need to be fleshed out in the future.
- tiagoespinha 9y agoNormally the argument is the this should be part of your backlog and not spread all over the code where no one (and especially the PO) can keep track of all the TODOs in all the files.
- Terr_ 9y agoDepends on trust. I've had an experience where old tickets documenting important architectural problems (e.g. SQL injection) were mass-closed as "probably obsolete" by managerial types. I was very happy I left a TODO in the actual code calling out the problem, because I could find and reopen the wrongly-closed ticket.
- deleted 9y ago[deleted]
- piaste 9y agoHeh. Visual Studio actually does keep track of all the TODOs in all the files in your project. It's the Task List window (View -> Other Windows -> Task List, or ctrl-alt-K).
- wruza 9y agoDoes it track FIXMEs?
- TheQwerty 9y agoBy default it looks for the tokens: HACK, TODO, UNDONE, and NOTE. However, you can add your own tokens and assign different priorities to them. https://docs.microsoft.com/en-us/visualstudio/ide/using-the-task-list#customTokens https://docs.microsoft.com/en-us/visualstudio/ide/using-the-...
- wruza 9y agoVery nice, it now almost resembles the functionality of "grep -rn FIXME ." in the shell and ":grep -r FIXME ." in vim.
- deleted 9y ago[deleted]