It makes a lot of sense if you are only a few people working the code. If not, maybe spend some minutes at the end of the day to register them as issues? If th

It makes a lot of sense if you are only a few people working the code. If not, maybe spend some minutes at the end of the day to register them as issues? If that’s to cumbersome or difficult, something is wrong in the process or tooling, IMHO. It makes me go crazy when I find todo scattered everywhere - often these todos are short, hard to decipher and ownership and priorities become jumbled. What you describe in the points above actually looks like an issue tracker to me. When I find todos I tend to cut them and paste them as issues trough slack bot integration. It keeps an ok flow, although I get annoyed that my fellows could not be bothered... To each their own I guess, and whatever works! Edit: I love in-line comments and documentation though. Just not todos. :)