AntiPatterns In Process
The last post on roughly this subject was not very coherent so here I will attempt to further layout what I was trying to say... In Fowlers book on Refactoring 'smelly code' is pointed out to be the reason we need to refactor. AntiPatterns are a formalization of 'smelly code'. With an AntiPattern we can identify exactly why our code smells. The refactorings that we listed in the J2EE AntiPatterns book all provide a way to get away from the AntiPattern. So the process of applying AntiPatterns involves first identifying the AntiPattern. Identifying usually involves finding a pain point. Where is the app performing poorly, what changes consitently lead to breakage etc. Once you identify a pain point you can start to look for the AnitPatterns that are causing the pain. Once you identify the AntiPattern you can start the refactoring process. There is a lot more that could be said...
