NULL: The Billion Dollar Mistakeby@mcsee
18,562 reads
18,562 reads

NULL: The Billion Dollar Mistake

by Maximiliano Contieri8mApril 13th, 2020
Read on Terminal Reader
Read this story w/o Javascript
tldt arrow
EN

Too Long; Didn't Read

Null: The Billion Dollar Mistake: It is time to stop using null. Null represents different situations depending on the context in which it is used and invoked. Null is not polymorphic with any object so any function that invokes it will break the chain of subsequent calls. This has led to innumerable errors, vulnerabilities, and system crashes. Null does not simplify life or make us more efficient, it is just more lazy, says Maximiliano Contieri. null: The excuse we use is that it is easy to write down to 10 to 10 times more code.

Coin Mentioned

Mention Thumbnail
featured image - NULL: The Billion Dollar Mistake
Maximiliano Contieri HackerNoon profile picture
Maximiliano Contieri

Maximiliano Contieri

@mcsee

I’m senior software engineer specialized in declarative designs and S.O.L.I.D. and Agile lover.

About @mcsee
LEARN MORE ABOUT @MCSEE'S
EXPERTISE AND PLACE ON THE INTERNET.

Share Your Thoughts

About Author

Maximiliano Contieri HackerNoon profile picture
Maximiliano Contieri@mcsee
I’m senior software engineer specialized in declarative designs and S.O.L.I.D. and Agile lover.

TOPICS

Languages

THIS ARTICLE WAS FEATURED IN...

Permanent on Arweave
Read on Terminal Reader
Read this story in a terminal
 Terminal
Read this story w/o Javascript
Read this story w/o Javascript
 Lite
L O A D I N G
. . . comments & more!