Hacker News Reader

Although I wonder how much self-censorship that encourages. Whether or not to put a TODO in your code is a judgement call. If you tell some developers that admitting to a TODO means that they can't submit, they might not admit to them as often.

It's a bit case-by-case, but I think I'd rather encourage contributors to admit to the lacks in their code and accept them - but get them to commit to follow ups that will fix the problems.

This is likely to lead to developers just leaving out the TODOs instead of doing the work. Especially for work that isn't needed now but should be done at some point in the future.

You aren't blocking technical debt, you are simply blocking TODO comments.

You're killing the messenger.

You should go be a team lead, get some deadlines - and the perspective that comes with it.

How's that job you work at without deadlines and where engineering is the most important department?