Fixing the Billion Dollar Mistake
summary
Claim: null pointer exceptions remain one of the most frequent runtime errors (Ops finds ~97% of logged errors come from ~10 kinds and nulls top frequency), and C#’s nullable reference types (C#8/9), null‑propagating/coalescing operators, records and init-only setters move many of those failures to compile time. Practical steps: enable nullable and treat warnings as errors, migrate one project at a time, validate edge DTOs, and consider the Railway‑Oriented Programming pattern or result types for domain errors; example code and tests are on GitHub.
AI-written summary · about
chapters (11)
- 0:00Introduction and setup
- 2:12The billion dollar mistake
- 8:58Handling null in modern languages
- 12:16Trend toward safer languages
- 15:50Null safety in C# evolution
- 18:29Fixing nulls with compile errors
- 23:09Effective null handling in C#
- 25:57Migration strategy for null safety
- 28:02Best practices for null reference types
- 35:07Railway oriented programming
- 42:36Q&A session
