On 12/20/2011 2:22 PM, Alex Turner wrote:
I could ask what's wrong with AOP, but you're probably thinking about
the same as me on that one. I like to call code like that "god"
code. It's the hidden mysterious force that can really screw things
up without almost anyone knowing where it came from and why, or being
able to fathom it's intention. Sometimes though - a little divine
intervention is handy :D
Agreed. I hate the idea of doing AOP when there's a more easily
understood and maintainable alternative or of 99% of developers in an
organization of any size doing/seeing any AOP.
Sometimes, however, there's a place for a few engineers to write "god"
code that is nicely tucked away and does what needs to be done and can't
be done as well any way but AOP.
--
Jess Holle
--
You received this message because you are subscribed to the Google Groups "The Java
Posse" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/javaposse?hl=en.
