Originally posted by Marcelo Ortega: Are these books a good introduction to the OOAD world, or are they mostly for experienced OO developers?
Robert Martin's book assumes that you have some programming experience and understand the basic mechanics of OO. That is, he doesn't explain what polymorphism is, but only how to make good use of it. It will be beneficial if you already experienced some of the problems with maintainability and extensibility he addresses.
He is known for stating that in his opinion, putting OO and A together in the same acronym doesn't make much sense. I tend to agree...
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus
Jeroen T Wenting
Joined: Apr 21, 2006
so do I. Problem analysis at the functional level should be independent of the implementation technique employed.
While an OO background can help in breaking up a problem into more easily digestible units it can also hinder in that it may make you look for things that aren't there and trying to force everything into an OO mindset when that may not be the best way to go.
P.S. He uses several languages next to each other in his book. No problem if you understand enough programming to understand concepts of languages you don't know, but might be a problem if you don't have that experience.
By the looks of things, one should probably read candidate 1 first. But according to Peer, maybee candidate 2 is better as an introduction.
Anyone care to debate this issue a little futher?
Joined: Aug 19, 2005
Originally posted by Marcelo Ortega: By the looks of things, one should probably read candidate 1 first. But according to Peer, maybe candidate 2 is better as an introduction.
Take a look at the sample chapters and judge for yourself. If you are finding ASDPPP too advanced�
please don't misunderstand, I'm not trying to be condescending here and given your current certification status you may take this the wrong way
� you may want to look into Jeff Langr's Agile Java(TM): Crafting Code with Test-Driven Development (Robert C. Martin Series) (Prentice Hall) first to give you a solid foundation in OO Java, Test Driven Development (and some agile methods) before moving on to ASDPPP. AJCCTDD and ASDPPP give you the tools for your day-to-day work. AUP (to a large part) is about the "rituals you follow and the artifacts that you create" to keep the more process-oriented members of your organization happy (and usually it is a good idea to have a "map" to show your progress to others and so you know where you are and where you are going).