In addition to logging and swallowing the exception, this method also then
returns null. This is also a bad practice.
The caller has to check for null. One of the reasons exceptions were invented
was to free the user from needing to check for null or error codes.
— Miguel
That sounds like a good approach, and is one that I've taken before on other
classes. But I want to be clear about something. Are you thinking of private
builders that are invoked by static methods? This would mean the API wouldn't
change much. Or were you thinking of having the user inst