The architecture was planned perfectly for the new system. All code would fit neatly into a slice and a layer. Sure this time we would not fall back into a big ball of mud! Fast forward some time, and we still ended up with (smaller) balls of mud. The developers are still complaining that the code is confusing, hard to understand, and hard to maintain. What went wrong?

In this session we'll rediscover the long lost art of recognizing code smells and applying various refactoring techniques. We'll also look at more complex refactorings that leverage modern tools such as generics and dependency injection. Finally, we'll see how to balance up-front design with emergent design to avoid big balls of mud over the lifetime of a system.