The same thing. As for TODO it’s completely out of row.
Zero TODO policy might be a good practice from the standpoint of issue tracking and project management.
From the perspective of code quality a better argument would be “todo’a in code encourage people to postpone refactorings and write bad code”. That’s arguable, but is at least about code quality, not something different.