3 ms·
> they often don’t give any indication how they are going to get to done It would be a really bad practice to merge procedures and policy with technical artifa
by marcosdumay 6y ago
> they often don’t give any indication how they are going to get to done
It would be a really bad practice to merge procedures and policy with technical artifacts. TODOs embedded in the code are technical artifacts, they say what should change, they really shouldn't say how and when.
> They never get prioritised and very rarely does anyone get to do them
Well, you are faulting the tool for your development practices. If your team doesn't look at TODOs, you indeed should avoid them. But that doesn't mean anything for other people.
At my workplace embedded TODOs would be bad too. At personal projects I find them quite useful with a similar life-cycle to warnings: you keep them there while the feature is being developed, but they must be gone by the time it's complete. Other people have different practices, and may successfully use them in different ways.