« We don’t have time for reviewing code » is both the most often and most reasonable excuse anyone may have. Think about it, features are already late : they are not being coded as you read this post. Then, when it’s done, there will be the other features that are stacking up while the current features […]
13
Oct
Oct
I’m already busy preparing for the international PHP conference, in Munchen, Germany. I’m giving two talks : on about PHP 5.6 and the second about static audits. Besides, being an impressive conference, I’ll be happy to visit one of my first conferences ever. Preparing for the next PHP Version Monday, October 27, 2014 […]
20
Jun
Jun
Detecting dead code in PHP PHP applications are under constant evolution. The code tents to grow bigger, more complex, and finally, to collect dust : this also know as dead code. Dead code is actual code that is not being used in production, even if the code is deployed. It is important to remove dead code. Missing […]
It is difficult to avoid the world cup yesterday. Since I’m not a football fan, but rather a PHP fan, I checked which technologies are in use for the national team. I got the list of the 32 national team, then checked they website. The great news is : PHP is a clear winner. Out of […]
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, […]
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 […]