Sometimes I am curious about what percentage of people who recommend/ praise/ preach about certain IT/computer science-related books have read them fuSometimes I am curious about what percentage of people who recommend/ praise/ preach about certain IT/computer science-related books have read them fully :) My impression: far from 100%
This book is very famous and influential. It aims to show the best solutions to common problems in software development (mostly in object-oriented programming). We have Creational, Structural and Behavioral design patterns (self-explanatory) that are the best tactics in certain situations (solo or combined). And, oh boy, there are many design patterns. Very often they are rather similar to each other and to do things even worse: a pattern with the same name may fall into different categories. o.O
I tried not to skip what I could not comprehend well, so sometimes I re-read the same paragraphs many times. It seemed that I understood things about the patterns but after finishing the book I am confused more than ever :D It wasn't helpful that code examples were in C++ which I don't care to learn any time soon. I'm glad I took notes - without them, I'd be completely lost.
Don't get me wrong: the design patterns are often very pretty and elegant (and those folks who "invented" them are totally smart!); it may save a lot of time because reduces the need for refactoring; also the book itself is well-structured and not bad... Still, I was brute-forcing my reading journey :D Finishing it became my self-serving goal because after a while I understood that the knowledge won't stick for long. Probably I'll be using the Singleton and a few others (the most simple ones) 90% of my coding :D
Was it worth it? Not sure, probably spending this time on coding would be more useful...Still, I decided to challenge myself and read one IT book a month (btw, I read this since the end of August). And building habits is important in the long run....more
Loading...
