Hi ,
This is more of a generic question about usage of sound programming practices. I am in the post-deployment phase of the application and now into defect management. Most of time in this phase I am investing in patching code with null checks, empty
string checks, trimming spaces, caseSensitive handling etc.
Don't know if this is an indication of bad design or bad programming practices but typically this tends to be the case in most
java projects and we end up doing a lot of paranoid programming with the aforementioned scattered through out the application.
I would like to know your feedback on this and is there a possibility of modularising all this nonBusiness (forgive me if this a heavy term) type of coding at central place(say entry point of the app) or externalizing etc so I can adopt a more optimistic programming style within the application least bothered to carry out null checks or empty strings or space/case sensitive issues.
Uday