Kotlin's Null Safety Makes Missing Data Part of the Type System

The article argues that many hard-to-reproduce crashes stem from code that assumes data will always be present, such as an optional profile field or an empty API response. It explains that Kotlin addresses this by encoding nullability directly in its type system, so a nullable variable cannot be accessed as if it were guaranteed to have a value. Safe-call syntax lets developers read nullable properties without triggering crashes, returning null when the value is missing. The elvis operator provides a fallback value when a null should be replaced with a default, such as a regular name in place of a nickname. Together, these features shift developers from remembering manual null checks to expressing in code which data may be absent.