Null is not a problem, developers are… I can’t count how many times I saw or reviewed code accessing the value property of a nullable value without checking if it was set. The compiler warning was there, but the developer just choose to ignore it.

I believe Microsoft finally solved the “problem” by allowing reference types to be nullable. Just configure the project and change the warning to a compilation error and you are good to go. The problem nowadays is that some libs haven’t been updated yet, but we’ll get there.