AOP - not really the next big thing in programming

I just read another article on AOP, and once more I wonder if the author has just chosen a bad example, or if AOP is as unhelpful and cryptic as I come to believe.

The OOP version of the sample code is easy to understand; everything that happens is clearly visible. The AOP version is a pain to understand (pointcut definitions that apply to code that bears no trace it is affected etc.), and what happens at runtime is a mystery until someone comes up with an IDE that displays AOP hints in the source, such as marking the entry of a method with information what pointcuts apply.