I Just read the blog post: Say No to Null and it was an interesting read but something about the idea of not handling Possible null exceptions rubs me up the wrong way.
The two reasons for not handling null were:
- Less code would need to be written.
- Code will look more elegant.
Neither of these two reasons satisfies my core values when developing code: Producing fast, Bug free code.
My null handling will remain the same. If I have 100% code coverage on the method and null parameters cause potential avoidable exceptions… I will fix them.