You must log in or register to comment.
Eh, then you just get those idiots who avoid using TODO: because it makes the code review “harder”.
// This is a broken example. // Note: remove X before doing Y
That’s no longer a technical process issue but more of a teamcoach/HR kind of issue then. You should be able to assume good intentions from colleagues, imho.