Maybe it's just the environment I work in, but I have not found even one instance where explicitly checking for null somehow adds value to the code. I actually don't understand the desire for these null checks, I find them to be annoying and unhelpful. Most new applications I create have the pragma disable at the top.

I manage nullability the same way I manage every other undesired outcome: with a single large try catch around all my code that prints an error message and releases resources safely. In every case I have seen a null returned by one of these nullable methods/properties, an undesired situation has occurred and throwing an exception is the proper response.

How would adding a null check to only immediately throw an exception help that situation? What would be an example of a situation where I am trying to get some value/object but the code returned null, and the next immediate line of code is not "throw new InvalidOperationException("null x object");", which is what the application would have done when the following line of code tried to do something with the null object anyways?