Nice writeup, though I was struck by the author's funny use of the word "concerns":

Remember that AOP aims to separate concerns from business logic ... It turns out that nearly half our function code is devoted to concerns!

Separation of concerns is about separating concerns from each other, not from business logic. Business logic and logging are both concerns.

It doesn't ruin the article or anything, it's just an interesting mistake.