> 1. Long-term improvements should be managed by a ticket tracking system. The code is not the correct place to manage that. Your code will probably outlive yo

> 1. Long-term improvements should be managed by a ticket tracking system. The code is not the correct place to manage that. Your code will probably outlive your ticketing system. It's also easier to grep for "TODO" than navigate any ticketing system that I've seen. TODO also tells you where the problem exists in code, which is not something that I often see on tickets. Additionally, the non-technical people that handle ticketing within most organizations are unlikely to recognize or prioritize code issues as actual issues. Some organizations might prevent devs from ticketing things themselves as well.