When I first started doing code review, there was a similar post on HN. I thought it was a good idea and tried to use a checklist, but a lot of the time you ski

When I first started doing code review, there was a similar post on HN. I thought it was a good idea and tried to use a checklist, but a lot of the time you skip over items because they don't apply. And as you do more code review you get better at identifying possible issues, reducing the need for a checklist. Nowadays you also have software (e.g. Hound) that does some basic checks for you.