He is not our friend. It does not simplify life or make us more efficient. Just more lazy. It is time to stop using . null Tearing down another inveteracy All of us have been heavily using null. It is comfortable, it is efficient, it is fast and yet we have suffered a bazillion of problems related to its use. What is the cognitive bias that currently prevents us, in addition to recognizing the problem, to start solving it? What does null stand for? is a flag. It represents different situations depending on the context in which it is used and invoked. Null This yields the most serious error in software development: Coupling a hidden decision in the contract between an object and who uses it . Coupling: The one and only software design problem As if this were not enough, it breaks the bijection that was our . only design rule Representing multiple elements of the domain with the same entity and forcing to have contextual interpretations. The one and only software design principle A good software principle challenges us to have high cohesion. All the objects should be as specific as possible and have a single responsibility (The S for ). Solid The least cohesive object of any system is our wildcard: null Null is mapped to several different concepts on the real world Catastrophic failures is not polymorphic with any object so any function that invokes it will break the chain of subsequent calls. Null Example 1: Lets us model the interaction between people during current covid-19 pandemic. { { ( ->meetingProbability() < random()) { ; } { PersonToPersonInteraction($somePerson, $anotherPerson);
        }
    }
} { { ( ->somePerson->isInfectedWith($aVirus) && $aVirus->infectionProbability() > random()) { ->anotherPerson->getInfectedWith($aVirus);
        }
    }
}

$covid19 = Virus();
$janeDoe = Person();
$johnSmith = Person();
$wuhan = City();

$interaction = $wuhan->interactionBetween($johnSmith, $janeDoe); ($interaction != ) {
    $interaction->propagate($covid19);
} final class City public function interactionBetween ($somePerson, $anotherPerson) if $this return null //no interaction else return new final class PersonToPersonInteraction public function propagate ($aVirus) if $this $this new new new new if null /* In this example we modeled the interaction between an infected person and a healthy one.
Jane is healthy but might be infected if Virus R0 applies to her.*/ We can see there are two flags and the corresponding clauses. null if Null propagation seems to be contained but looks are deceiving. A little bit of history The creation of happened due to a fortuitous event in 1965. null : The creator of the QuickSort algorithm and also a winner of the Turing Prize (the Nobel Prize in Computing) added it to the language because it seemed practical and easy to do. Several decades later he showed his repentance: Tony Hoare Algol This excellent article tells the story in detail: Null Pointer References: The Billion Dollar Mistake I call it my billion-dollar mistake…At that time, I was designing the first comprehensive type system for references in an object-oriented language. My goal was to ensure that all use of references should be absolutely safe, with checking performed automatically by the compiler. But I couldn’t resist the temptation to put in a null reference, simply because it was so easy to implement. This has led to innumerable errors, vulnerabilities, and system crashes, which have probably caused a billion dollars of pain and damage in the last forty years. – Tony Hoare, inventor of ALGOL W. The full video is also available . here The excuse We, as developers, use because it is easy (to write down) and because we believe it improves the efficiency of our software. null By making this mistake we ignore that the code is read up . to 10 times more than it is written Reading code with is more arduous and difficult. Therefore, we are only postponing the problem later. nulls Regarding efficiency (which is the most used excuse to ). Unless in very specific and critical cases, its performance loss is negligible. And it is just justified in those systems that prioritize efficiency over readability, adaptability and, maintainability (there’s always a trade off regarding quality attributes). generate coupling This cognitive bias persisted over time although, according to the current state of the art, modern virtual machines optimize the code for us. To use evidence instead of gut we just need to start benchmarking instead of keeping on erroneously claiming that efficiency is more important than readability. Fail Fast is (ab)used to mask unexpected situations and spread the error in the code too far away, generating the much-feared ripple effect. Null One of the principles of good design is to fail fast. Example 2: Given a data entry form for a patient we are requested to fill the date of birth. If there is an error in the visual component and the object creation, it could be built with a date of birth. null When running some nightly batch process that collects all the dates of the patients to calculate an average age, the admitted patient will generate an error. The stack with useful information for the developer will be very far from where the defect is present. Happy Debugging ! Photo by Victoria Heath on Unsplash What is more, there might be different systems with different programming languages, data transmission through an API, files, etc. The developer’s worst nightmare is having to debug that bug early in the morning and try to find the problem’s root cause. Incomplete objects is used in many ways, as we listed above. If we allow incomplete models, non-completeness is usually modeled with a . This adds complexity by populating the controls code with ifs. Null null The presence of nulls generates and messes up the code with multiple controls. repeating code ifs Fostering incomplete models forces us to make two additional mistakes: 1. Pollute code with to complete the essential information needed. setters Nude Models - Part I : Setters 2. Build models violating ignoring real world entities their essence. mutable bijection do not mutate Is it Crystal Clear for Everybody That a Date Should Not Mutate? Typed languages that do not handle optionally Most typed languages prevent errors by ensuring that the object that is sent as a parameter (or returned) is able to answer a certain protocol. Unfortunately, some of these languages   have taken the step backward of allowing to declare that the object is of a certain type and (optionally) . null This breaks the chain of invocations forcing to control the absence of the object violating the Solid . Ifs open/closed principle Whats is more, corrupts type controls. If we use a typed language and trust the compiler defense network. manages to penetrate it like a virus and spread to the other types as pointed out below. null Null The worst mistake of computer science - Lucidchart The solution Do not use it. The alternatives As usual to solve all our problems we should stay loyal to the only axiomatic design rule that we have imposed ourselves. Search the problem domain for solutions to bring them to our model. Model polymorphic absences In the above case when objects must declare a type, there are more elegant solutions that avoid to model optionally. ifs In classification languages, it is enough to use the in our concrete class sibling and declare the supertype as a type of the collaborator based on the (L of SOLID). NullObject design pattern Liskov substitution principle However, if we decide to implement that solution we will be violating another design principle stating: We should subclassify for essential reasons and not to reuse code or adjust class hierarchies. The best solution in a classification language is to declare an interface to which both the and the must adhere. real class null object class In the first example: { ;
} { { }
} { { ( ->somePerson->isInfectedWith($aVirus) && $aVirus->infectionProbability() > random()) { ->anotherPerson->getInfectedWith($aVirus);
        }
    }
} { { SocialDistancing(); }
}

$covid19 = Virus();
$janeDoe = Person();
$johnSmith = Person();
$wuhan = City();

$interaction = $wuhan->interactionBetween($johnSmith, $janeDoe);
$interaction->propagate($covid19); Interface SocialInteraction public function propagate ($aVirus) final class SocialDistancing implements SocialInteraction public function propagate ($aVirus) //Do nothing !!!! final class PersonToPersonInteraction implements SocialInteraction public function propagate ($aVirus) if $this $this final class City public function interactionBetween ($aPerson, $anotherPerson) return new // The cities are smart enough to implement social distancing to model Person to Person interactions new new new new /* Jane will not be affected since the interaction prevents from propagating the virus No viruses are involved and neither ifs nor nulls ! In this example, we replaced with a specialization that, unlike it, exists in the problem domain. null Patient’s birth date revisited Let’s go back to the patient form example. We needed to compute the average leaving out not filled forms. { ;
} { {
        $aVisitor->visitDate( );
    }
} { {
        $aVisitor->visitDateNotPresent( );
    }
} { $count = ; $ageSum = ; { ->count++; ->ageSum += today() - $aDate;
    } {
    } { ( ->count == ) ; ->ageSum / ->count;
    }
} {
    $calculator = AverageCalculator(); ($patients $patient)
        $patient->birthDate()->accept($calculator); $calculator->average();
} Interface Visitable public function accept ($aVisitor) final class Date implements Visitable public function accept ($aVisitor) $this final class DateNotPresent implements Visitable public function accept ($aVisitor) $this final class AverageCalculator private 0 private 0 public function visitDate ($aDate) $this $this public function visitDateNotPresent ($aDate) public function average () if $this 0 return 0 else return $this $this function averagePatientsAge ($patients) new foreach as return We used the to navigate objects than can behave as null objects. Visitor pattern No nulls Furthermore, we removed using polymorphism and left the solution open to calculations through the open/closed principle. non-essential if other besides average We build a less algorithmic but more declarative, maintainable and extensible solution. Use languages with explicit modeling of absences Some languages support optionally with the concept of Maybe/Optional which is a particular case of the proposed solution implemented above at the language level. Conclusions Using is a discouraged practice based on deep-rooted practices in our industry. Despite this, almost all commercial languages allow it and developers use it. null We should, at least, begin to question its use and be and responsible in developing software. more mature Part of the objective of this series of articles is to generate spaces for debate and discussion on software design. We look forward to comments and suggestions on this article. This article is also available in Spanish and chinese . here here

Too Long; Didn't Read

Making security fun one episode at a time

NULL: The Billion Dollar Mistake

Too Long; Didn't Read

Maximiliano Contieri

About Author

TOPICS

Languages

THIS ARTICLE WAS FEATURED IN...

NULL: The Billion Dollar Mistake

Too Long; Didn't Read

Maximiliano Contieri

About Author

TOPICS

Languages

THIS ARTICLE WAS FEATURED IN...

RELATED STORIES