Timeline for What design patterns are the worst or most narrowly defined?
Current License: CC BY-SA 2.5
2 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 17, 2011 at 16:28 | comment | added | Dunk | Your solution uses the old it decouples things argument. In particular, you post an event and some other guy handles the event and logs it. That's a good thing, because everyone is decoupled! WRONG! I used to do that, what a royal pain it became. I realized that if I want something to be logged, I want to explicitly say log this exact thing, right here, right now, in the code at the point that it occurred. Not have some other object figure out what should be logged, with possible other events interjected by other handlers, if it is even logged at all. It is nothing but convoluted overdesign. | |
| Feb 17, 2011 at 10:00 | history | answered | CashCow | CC BY-SA 2.5 |