DEV Community

Discussion on: A code review checklist prevents stupid mistakes

Collapse
 
lucaspottersky profile image
Lucas Pottersky

this specific checklist looks like enterprise bull$hit to me. it sounds more of a way to intimidate/coerce the devs than to actually help them out.

Collapse
 
bosepchuk profile image
Blaine Osepchuk

Okay. That's not our intention.

I work in a small company as one of two programmers and we made the checklist ourselves so that's about as far from "enterprise" as you can get.

Collapse
 
calebcauthon profile image
Caleb Cauthon

I enjoy a good checklist but I understand this guys reaction! You gotta have some pain before you want to take on an extra step like this.

Collapse
 
dougdescombaz profile image
doug descombaz

We've done something similar at a start-up I was at. Well, it was between start-up and whatever is next with around 30 devs by this time. The idea was to encourage people to not just rubber stamp reviews.

One missing thing is to check out the branch when you are reviewing (if the code bases isn't tattooed in your brain).

Thread Thread
 
bosepchuk profile image
Blaine Osepchuk

Yes. You must checkout the branch and examine it in your IDE. Otherwise you can't do several of the checklist items like check for inspection errors, run the tests, etc..