Boulder JUG
I'll be speaking tonight at the Boulder JUG about J2EE AntiPatterns. Hope to see anyone in the area there!
Recent Posts
RSS FeedsAntiPatterns 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...
Unit Testing Legacy GUI Code
It has been my intent for some time to post about this but I keep forgetting so without further ado; Refactoring Group Files Checkout the WLECNov272002.pdf file for lots of great info about how to test legacy GUI's.
Comments anyone?
Sorry I forgot to enable comments... They should be active now.
