I'm Not Smart Enough To Use AOP

Filed in archive Programming on April 28, 2006

I saw this posting on JavaLobby titled: AOP: Is anyone using it? Below is my response.

On one of my most recent projects a team member and I decided to use the SpringFramework. So I went out and bought a book about it and simply started using it. One day I decided to try to actually implement something using AOP. I decided to do it with logging, because that is what most of the examples I could find used, and after some time got things working the way I wanted.

That was great. I did a victory lap to and from my local Starbucks and once settled down again at my PC with a hot cup of coffee I started to think of all the incredible things I could now do with my newfound AOP understanding.

Then it hit me. When it comes right down to it I have no idea what I would possibly use AOP for on an average project. With all the OO concepts, Design Patterns, libraries, etc... do I really want to inject another advanced concept like AOP into what I'm doing. Better yet would I even know how to do it and how much energy do I want to spend on trying?

Then I came to accept something. I'm simply not smart enough to use AOP and that is OK. If someday someone comes along on a project and convinces me that I need to figure this stuff out I will. Otherwise I'm letting this train pass me by.

Related Entries:

« Personal Branding for Tec... | Main | AJAX Pattern Screencasts »

Permalink: I'm Not Smart Enough To Use AOP

Tags: AOP Java

Vote for I'm Not Smart Enough To Use AOP:

Currently 6.67/10
1
2
3
4
5
6
7
8
9
10

Rating: 6.67 out of 3 vote(s) cast.

Response from: Andy (04/30/06 10:08am)

The point of AOP isn't that you need to be smart enough. Its that other people can do your work for you so that you can be dumb. For instance the application of logic via annotations is commonly accomplished via AOP. It is unlikely taht you as an application programmer will ever have to write even a single aspect...and that is okay. There are instances where it is helpful: security by context filters comes to mind. However, most apps don't need home-grown AOP services.

Response from: Jason (04/30/06 5:42pm)

Thanks for your insight Andy. I try to have an open mind about these things. If the intention is for Application Service providers and or frameworks of some kind to implement functionality then that is understandable. Because your right, and it is the point of my post, that I cannot think I when I would create and use a home-grown AOP Services.