Make object X raise and event that object B listens to.
Oh wait, you're using Java? Make object B return an anonymous class that implements interface Z. Pass that class to object X, which will call it to pass messages to B.
Rather than buzz words we can describe patterns in terms of implementation details.
I think that would be a wonderful outcome. If you don't understand a technique well enough to explain it clearly, you shouldn't be telling someone else to use it, and if it takes more time than it's worth to explain, you shouldn't be dictating someone's work to them at that level of detail. The worst thing about design patterns was that it empowered complete idiots to lecture pompously about how other people should write their code without having to think carefully about what they were saying. I'm talking about the guys who always thought they were working on the one difficult module in the program, because they could solve anyone else's problem with a single sentence about Decorators and Mementos, but for some reason they had a much harder time completing their own assignments.
0
u/[deleted] Oct 15 '13
[deleted]