Haven't seen programmers do this a whole lot. In any case this should get cured by one bug hunting session where the method horribly fails.

Also i am not sure that this is 'confirmation bias' being cause of anything. The methodology of thought for determining where the bug is, has to be taught. For me to confirm that bug is where I think it is, takes two print statements, before, and after.