In reality, who has the time to “wait a day” before re-reading the code? (Imagine there’s no deadlines, and no clients, too. Imagine all the coders…)

“Pretend you’ve never seen your code before” – how do you do that? Bang your head against the wall really hard and hope to induce amnesia?

“Use checklists for code review” – and if you do, keep it to yourself because the next thing you know, it becomes the company policy, there’s a half-broken web tool your company requires you to use which randomly breaks other web tools it pretends to integrate with.

“Read documentation, comments, and displayed text out loud” – in an openspace, right. That calls for a Monty Python sketch.

“Take the opportunity to write more documentation.” – implying you have a lot of spare time and energy left after you have read your entire code submission out loud in the restroom to the accompaniment of your colleagues banging on the door to make you get the *#@! out of there.

But as I’ve said, I agree: let’s keep dreaming!

P.S. Don’t take this comment too seriously. It probably just means I need a vacation.

I found that new hires often just don’t think to read their code in the code review tool, I always explicitly ask for it now. It really help catching mistakes if you see your code in the same tool as your reviewer. You don’t want to waste your reviewer’s time with simple formatting or spelling mistakes while they could be looking at more important things.