The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
And it's about as much about programming as it is about Zen Buddhism or motorcycle maintenance. But ... learn the right lessons from it, and you can cope with development (and make a start of fixing motorcycles as well).
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
I have read the introductory chapters (intro and chapter 1) and then skipped around a bit. Mostly too hard for me. I like that they say, "Prefer composition over inheritance."
That's what that entire book is about for me. I remember back when OOP was growing in popularity (1991 or so) and it was all about inheritance. Then GoF explains, "no it's about composition". That's good stuff!
It's good as a reference. Just read the general description of each pattern and look at the details when you think you need a pattern but the UML diagram doesn't give you a good enough idea of how to write the code.
As much as anything, the fact that it gives a name to each pattern saves lots of time during design discussions, because everyone can quickly understand an approach being suggested. It's about much more than composition, though.
I've gotten some mileage out of the visitor pattern but I didn't learn it from that book. In fairness though, they describe it for people that didn't already learn it, and it's one of the more useful patterns to know, IMO.
That's interesting, because I don't recall using Visitor. It probably depends on your problem domains. The patterns that resonated most with me were Chain of Responsibility, Abstract Factory, and Observer, and the simpler Singleton and Flyweight. I'd already used them but now had good names for them.
For me, it's a toss up between Kernighan & Ritchie's The C Programming Language, and Aho, Kernighan and Weinberger's The AWK Programming Language. Other books I remember from college days include Fortran IV With Watfor and Watfiv, and a two book set of Shelley & Cashman on Cobol. Those are all still around, somewhere in the attic, along with a lot of seriously outdated hardware. I know there's a 300 baud modem with the acoustic couplers for a standard Bell desk phone's handset up there, and a couple of cases of 80-column cards.
Last Visit: 23-Nov-20 15:54 Last Update: 23-Nov-20 15:54