Prev: Survey about Visual Annotations for Software Models
Next: Combine Factory and Interface?
From: H. S. Lahman on 27 Sep 2007 10:24
Responding to C....

When you say OOP, do you mean generic OO development or do you mean a
separate stage of OO development that is distinct from OOA and OOD?

If the former, then check out the "Books" category of my blog.


*************
There is nothing wrong with me that could
not be cured by a capful of Drano.

H. S. Lahman
hsl(a)pathfindermda.com
Pathfinder Solutions
http://www.pathfindermda.com
blog: http://pathfinderpeople.blogs.com/hslahman
"Model-Based Translation: The Next Step in Agile Development". Email
info(a)pathfindermda.com for your copy.
Pathfinder is hiring:
http://www.pathfindermda.com/about_us/careers_pos3.php.
(888)OOA-PATH



From: Daniel Pitts on 27 Sep 2007 11:17
On Sep 27, 7:10 am, "Michael C." <Micha...(a)anonymous.com> wrote:
>

Its generally considered good etiquette to include SOME text in the
body, even if it is verbatim copy of your subject.

The OOP books that have helped me the most are actually Refactoring
books in particular. Refactoring (Martin Fowler) and Refactoring To
Patterns (Joshua Kerievsky). Kerievsky references Fowler quite a bit,
so I would get "Refactoring" if nothing else. I find them valuable
because not only do they tell you good patterns (and bad
antipatterns), they tell you have to convert your system from one
approach to another, including changing an antipattern into a pattern.


From: Joe Scylla on 28 Sep 2007 02:33
http://c2.com/cgi/wiki

<quote>
Welcome to the original WikiWikiWeb! This site is a ContentCreationWiki
whose focus is PeopleProjectsAndPatterns in SoftwareDevelopment.
</quote>

imho this wiki is a quite good read on OOP and pattern designs - and
also on many other topics about software development.

Joe
From: Totte on 28 Sep 2007 05:48
On Sep 27, 4:10 pm, "Michael C." <Micha...(a)anonymous.com> wrote:
>

My personal favorite is Head First Design Patterns.

It's basically GoF DP made understandable ;-)

/Martin Rosén-Lidholm

From: topmind on 28 Sep 2007 11:55
On Sep 28, 2:48 am, Totte <martin.rosenlidh...(a)gmail.com> wrote:
> On Sep 27, 4:10 pm, "Michael C." <Micha...(a)anonymous.com> wrote:
>
>
>
> My personal favorite is Head First Design Patterns.

Hell no! That book teaches the horrible practice of making the
programmer be a glorified store product clerk. Classifications of
features and products should *not* be hard-wired into the app code if
possible except for underhanded attempts at job security.

Product classifications and feature associations for real apps should
be data-driven for the most part so that product managers/clerks can
change them without custom program code changes.

Yeah I know, it is only training toy examples, but I didn't see any
significant disclaimers. But this is also related to the bad OOP
practice of hard-wiring domain classifications into code in general.
OO needs a big spanking for that and this book only encourages this
bad fad even more.

That book is a head-first disaster.

>
> It's basically GoF DP made understandable ;-)
>
> /Martin Rosén-Lidholm

-T-

 |  Next  |  Last
Pages: 1 2 3 4
Prev: Survey about Visual Annotations for Software Models
Next: Combine Factory and Interface?