Ok, this is a relatively old thread, but I just accidentally came across the mentioned comment and got angry about it.
This is exactly the attitude causing so many problems in our industry: people don't knowing their craft *and* don't giving a shit about it. Imagine a physician telling you "DNA and all this modern enzyme stuff - way over my head, didn't like it chemistry at school anyway" - you would run away immediately.
However, in software it is - sadly enough - quite common to meet poeple of that kind. Thus, if you do not understand architecture, design forces and the like, please stay writing Excel macros or change jobs...
There are different ways in which the "Observer Pattern" can be
implemented. In this article, I have used an implementation approach
as described by GoF, in the book "Design Patterns". The Observer Pattern
is described detailed in this book starting from page no. 293. Pierre
uses a Change Manager in the implementation of the Observer Pattern
to decouple the Subject and the Observers, so that the Subject can
be reused independently of the Observers. I thought of writing it
is as a seperate topic under "Publisher/Subscriber Pattern", an
implementation variant for the Observer Pattern. Hope this clears the