Skip to Content

cf.Objective Code Review

Posted on

Thanks to everyone who showed up for my cf.Objective presentation on Code Review.

While my slides were mostly pictures and are probably not very helpful I’ve put together a long list of useful links which will hopefully get you started with Code Reviews.

Bookmark this link to my wiki for more resources.

To summarize my presentation:

  • Code with issues may easily pass automated tests like MXUnit and Selenium! SELECT *, no hints, etc. Hence the need for code reviews!
  • Define some rules for your reviews. Make sure everyone knows what they should be looking for (and not looking for).
  • Limit code reviews to 200-400 lines of code. Think CFC, not application.
  • Limit reviews to 60 minutes! Anything more and you and the other reviewers become less effective.
  • Remember you are reviewing code, not the coder!

And finally, like everything else – there is no ‘right way’ to do code reviews. Experiment, and find out what works for you.