Following Cake's code standards

If a team of developers follow a set of agreed code standards, it makes life a whole lot easier to compare (i.e. a diff) of two versions of the same code and see what has changed. If you try to compare two version of the exact same code formatted differently, the result will be a lot of highlighted differences when in terms of functionality they are the same. This is quite important since comparing code is the first step of integrating changes written by several developers.

You are probably thinking that this not-news is a bit obvious, and it is, but as I found myself breaking agreed code standards through the process I was using to develop, I thought it would be worth discussing ways of systematically ensuring that you follow code standards (or know that you are breaking them).