#AOP: AOP myths and realities

“Myth 9: Rather than worry that it obscures program flow, you can look at the effect of AOP on program control flow another way: AOP gives you a direct mapping between requirements, design, and code elements. In other words, crosscutting requirements aren’t lost in the forest of code. Separating crosscutting requirements into aspects allows you to preserve the “global picture” of your system in code. On the other hand, the “local picture” created by interaction between aspects and classes becomes implicit, and so less obvious.”

Such a great read, worth spending time reading the whole article:

via AOP@Work: AOP myths and realities.

One thought on “#AOP: AOP myths and realities

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: