Books On Object Oriented Programming

Dec 12, 2011 at 7:35pm
Any suggestions or links would be helpful
Dec 12, 2011 at 7:52pm
"Design Patterns" by the GoF?
Dec 12, 2011 at 9:05pm
Yes, and "Head first design patterns"

Although this is a Java book it is much easier to read than GoF, I've got both.
Dec 13, 2011 at 8:20pm
If you want to learn how to think in oo terms, before moving on to investigate patterns and the like, one book you could check out is "Object-Oriented Programming" by Coad and Nicola. It's been around a while (since 1993) but it's still about, and the basics of oo haven't changed.

Coad is one of the original oo people, along with his colleague Yourdon. And then there are Rumbaugh, Booch, Jacobson, whose work came together -- along with others -- to form UML, etc.

There is also Object-Oriented Analysis and Object-Oriented Design in the same series, but I thing OOP is the one to go for. It's selling for $85 on Amazon.com, so it might be one to track down at a library. At least to start with.

While I like it's approach, it might not be to everyone's taste. Amazon.com's "Look Inside" will give you an idea of what you're letting yourself in for!
http://www.amazon.com/Object-Oriented-Programming-Peter-Coad/dp/013032616X

Did you ever watch Sesame St??

Andy

PS Design Patterns is not a book to start with. Once you get oo, then look at patterns to see how you can reuse designs more efficiently.
Last edited on Dec 13, 2011 at 8:22pm
Dec 14, 2011 at 1:38am
And the irony of it all is after reading from GoF and you look back at your programs you have developed in the past, some of the patterns have already been utilized by yourself without you even knowing. Now at least you can give a "name" to some of them since they have been named and categorized "officially" by the GoF.

So I believe GoF works are not entirely new, prior to their seminal released work, a lot of working programmers have already either conscious or sub-consciously doing it in their programs. What GoF bring is to flesh out those patterns in details and give a formal name and category to that pattern. This is an admirable effort.

It also make discussion among programmers more productive when we can convey our pattern to other programmers by saying a name instead of trying to describe to them what it is :P
Topic archived. No new replies allowed.