The audit report contains several parts : the main part is the diagnostic, and the secondary part is the appinfo. Let’s review them. The diagnostic The diagnostic collect all information in the code that needs to be reviewed, and probably fixed. The diagnostic has 3 parts : the dashboard, the full list and the detailed report. The […]
Defining a PHP method is quite standard : a function only requires a name and arguments. The arguments are its signature, just like this : function x($arg1, $arg2, $arg3) {} Arguments may, among other things, have default value. When this is the case, the arguments has to be at the end of the signature. Thus, function goodSignature($arg1, […]
27
May
May
Reviewing code is like checking your own copy before handing in an exam : last exam I took was driving test (incredible, I know), and I passed by 0 the 100 questions quiz. I do remember changing three or four answers while reviewing the answers, and even as I don’t know for sure about it, I […]
08
May
May
When programming, I devote a part of my time to review the code. Of course, there is the necessary review when a bug arise, but I’m talking here about self-review. It feels always good to re-read fresh code, make sure I didn’t forget anything, may it be security, performance, recent PHP or framework recommendations. […]
Auditing code is actually a fancy word for reading the code. Sometimes, I even wonder if a programmer isn’t reading code more often than write. Good piece of code will be written once, and changed seldom afterwards. Bad piece of code will be reviewed, re-read for debugging, and sometimes forgotten : this is when we spend […]