Clean Code Concepts Adapted for PHP

Clean Code PHP (jupeter/clean-code-php), is a guide based on the book Clean Code: A Handbook of Agile Software Craftmanship, a classic programming book about writing maintainable code by Uncle Bob Martin.

The clean-code-php guide is inspired by a JavaScript adaptation, clean-code-javascript with PHP-specific features.

Here are a few of my favorite adaptations from the clean-code-php repository:

#Don’t add unneeded context

#Bad

<?php
 
class Car
{
    public $carMake;
    public $carModel;
    public $carColor;
 
    //...
}

#Good

<?php
 
class Car
{
    public $make;
    public $model;
    public $color;
 
    //...
}

View Don’t add unneeded context in the guide.

#Function Arguments (2 or fewer ideally)

#Bad

<?php
 
function createMenu($title, $body, $buttonText, $cancellable) {
    // ...
}

#Good

<?php
 
class MenuConfig
{
    public $title;
    public $body;
    public $buttonText;
    public $cancellable = false;
}
 
$config = new MenuConfig();
$config->title = 'Foo';
$config->body = 'Bar';
$config->buttonText = 'Baz';
$config->cancellable = true;
 
function createMenu(MenuConfig $config) {
    // ...
}

View Function Arguments in the guide.

#Functions Should Do One Thing

#Bad

<?php
 
function emailClients($clients) {
    foreach ($clients as $client) {
        $clientRecord = $db->find($client);
        if ($clientRecord->isActive()) {
            email($client);
        }
    }
}

#Good

function emailClients($clients) {
    $activeClients = activeClients($clients);
    array_walk($activeClients, 'email');
}
 
function activeClients($clients) {
    return array_filter($clients, 'isClientActive');
}
 
function isClientActive($client) {
    $clientRecord = $db->find($client);
    return $clientRecord->isActive();
}

View View Functions Should Do One Thing in the guide.

#Opinions, Opinions, Opinions

The author outlines the following about the purpose of the guide:

Not every principle herein has to be strictly followed, and even fewer will be universally agreed upon. These are guidelines and nothing more, but they are ones codified over many years of collective experience by the authors of Clean Code.

In a dynamic language like PHP (or any language for that matter), developers will disagree with some (or many) of the points made about the concepts demonstrated. I think the point I’d make is not to write off all ideas contained in the guide if you disagree with one or more ideas.

#Learn More about Clean Code

I highly recommend that you read the Clean Code book to get a deeper understanding of the guidelines demonstrated in the PHP adaptation. On its own, the PHP guide is a good read, but part of the journey is learning how to spot code that needs some work and then adapting it.

Another great book related to Clean Code, is The Clean Coder: A Code of Conduct for Professional Programmers which focuses on you, the coder. In my opinion, these two books should be a must-read for programmers of any experience level looking to improve their code craftsmanship.