2013/9/1 Mohamed Ashraf <mohamed.ashraf.213(a)gmail.com>om>: The error reporting server is completely new, so we'll have to define a coding style for this. I would suggest to use the same structure for the DocBlocks as we use in phpMyAdmin, but the cakePHP uses a different coding style, so it's better to follow the example of what's done in cakePHP. Did you have a look at how the DocBlocks in cakePHP are defined? But code documentation is not just the DocBlock describing what a method does, but also putting enough comments in the code, explaining what is happening, why it is done this way, or just structuring your code. Relying on other developers* to read code and understand everything that is there is time consuming. Well documented code can be read quickly, thus making future code maintenance quicker. (* this includes you in 6 months time when you don't remember exactly how fe. that format string is constructed, or what all the parameters of that method are for) That said, a rule of thumb for documenting your code : if you need time to remember what a line of code does, or took you some time to write it (fe. going through all the different parts of an if-statement, reading a regexp, or why you have to call some method before calling another one), add some comments about what it is supposed to do. I'm not saying you have completely explain 'bit by bit' what is happening, unless you feel it is necessary to do so in a given case. ;) I hope this helps. -- Kind regards, Dieter Adriaenssens