Null references or: How I Learned to Stop Worrying and Love Scala Options

“I call it my billion-dollar mistake. It was the invention of the null reference in 1965” — Tony Hoare, 2009

For many software developers, the null reference is something they encounter very early in their careers, and continues to haunt them for the rest of their lives. In simple terms, a null reference is when an object is declared but not assigned a value. A situation like the one below could potentially throw what’s called a NullPointerException




Hootsuite's Engineering Blog

Recommended from Medium

Supporting Person Accounts in Your ISV Solution — Part One

Kanban workflow on Evernote. Is it possible?

Towards python 3.8

All You Should Know About SAP S4HANA Simple Logistics

Building Kytra, an intelligent investment brokerage.

Wiring your Android app. with Activities

Script Communication in Unity with GetComponent!


Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
James Yoo

James Yoo

Co-op software developer at Hootsuite on the Engage team

More from Medium

Async Superpowers, Part 2

Programming 101: Declarative vs Imperative Paradigm

Software Development Models: Comparing Waterfall & Feedback Models

Scala Option Some None

Scala Option Some None example