Some code is downright scary to maintain. An all too common example are bloated service methods that do too much: manage transactions, handle security as well as implement the business rules. Changing that kind of code requires you to understand and tackle many different concerns. Code can also be difficult to maintain if the implementation of some features (e.g. audit logging) is scattered throughout the code base. Changing that kind of code involves changing many components. This talk describes how to improve your code with real objects and aspects. We show how to use AOP to simplify your code by modularizing concerns such as audit logging that are normally implemented by code that is mixed in with the business logic. We also describe how to write truly object-oriented code in Java - something which is not done as often as you might expect even though Java is an object-oriented language. We will compare and contrast a procedural design with an object- oriented design and describe the benefits of using real objects. We will also show how to refactor a procedural design into an object-oriented design — an easy way to eliminate those fat service methods and improve the design of your application.

You can download the slides from here: presentation (pdf).