[Fwd: RE: [svp] [Fwd: [prog] Book Recommendation for OOP Design]]

Darlene Wallach wallachd at earthlink.net
Mon Apr 5 15:26:54 EST 2004

-------- Original Message --------
From: Mitchell, David [CC] <david.mitchell at mail.sprint.com>
Date: Mon, 5 Apr 2004 09:27:04 -0500
Subject: RE: [svp] [Fwd: [prog] Book Recommendation for OOP Design]

I'm also a big fan of Beck's style. The cook's tour references an 
earlier work that was very influential to me:

Beck, Kent, _Smalltalk Best Practice Patterns_, Prentice Hall, 1996

I read a pattern a day from this book while I was working on my 
first Smalltalk project. Trouble is, if you aren't working in 
Smalltalk, the code examples will seem strange. And, since it is 
primarily a book about coding, that hurts.

When I read Fowler's Refactoring, I noticed many of its 
refactoring patterns were adapted from Beck's earlier work. And, 
the example code is in Java. I highly recommend Refactoring as 
your next book as it is very approachable and really focuses on 
the design through code.

A less popular Java book that was also influenced by Beck is:

Langr, Jeff, _Essential Java Style, Patterns for Implementation_, 
Prentice Hall, 1999

Quoting the author from the introduction:

"The bulk of the patterns described are the same as those 
contained within Smalltalk Best Practice Patterns."

In other words, what if you took the titles and structure of the 
Smalltalk book, and rewrote it for Java. This book was helpful to 
me, but I don't think it is as well written as _Refactoring_ and 
has not attracted the same audience. Also, he gets off track a 
bit when he gets to collections (Smalltalkers have a hard time 
accepting Java idioms for collections.)

As to Shalloway's _Design Patterns Explained_, I like this book a 
lot. Very readable and introduces 10 or so of the patterns very 
clearly. I think its treatment of the Bridge pattern is quite 
lucid. However, I am not sure it is the best next book for you, 
as its examples are also from the "large system" mold (CAD/CAM 
machine tooling).

I guess I'm presuming that you are using Java. Is this true, or 
is it something else?

--David Mitchell
david.mitchell at mail.sprint.com

-----Original Message-----
From:	Jean Tessier [mailto:jean at jeantessier.com]
Sent:	Mon 4/5/2004 2:21 AM
To:	siliconvalleypatterns at yahoogroups.com
Subject:	Re: [svp] [Fwd: [prog] Book Recommendation for OOP Design]
I would start straight away with Fowler's "Refactorings" if I 
were you.

I list my own book preferences on my webpage, 
(under Software), and I also started a reading journal where I 
Mike Shalloway's book.  I read the first edition of Larman's book:
solid, but not my favorite; a little too formal to my taste.

I highly recommend you look at:

	Agile Software Development: Principles, Patterns, and Practices
	by Robert C. Martin

Don't let the title fool you, section 2 is all about common sense OO
techniques and guidelines to structure for you to code by.

You might also want to check out Kent Beck's books.  I really 
liked how
he described coming up with JUnit in:


And I think his TDD book starts of from there and elaborates further.

	Test Driven Development: By Example
	by Kent Beck

I hope this helps,

Darlene Wallach wrote:
> In case people have suggestions and/or comments for Elizabeth ...
> Darlene
> -------- Original Message --------
> To: programming at linuxchix.org
> From: etb <lizzy at soggytrousers.net>
> Date: 07 Jan 2004 07:50:10 -0600
> Subject: [prog] Book Recommendation for OOP Design
> Hi Everyone,
>     My little parser class based on regular expressions did not work
> out as well as I had hoped so I am re-evaluating it and I would very
> much like to make it more object-oriented in nature as currently its
> mostly procedural using objects.
>     I've invested in various OOAD books (Booch, Jacobson and 
> Coad) and
> have either read them or in the process of reading them but these 
> seem
> to be for designing large-scale systems (such as a luggage-tracker at
> an airport) as opposed to "hey, why not make that parser part an
> object and pass it around like this" sort of like the GoF's pattern
> book.
>     It seems like I'm having some difficulty jumping the hurdle 
> between
> procedural coding and OO coding. As such I'm wondering if anyone 
> has a
> book recommendation that may help me navigate this strait.
>     I'm considering purchasing these:
>          Design Patterns Explained: A New Perspective on
>            Object-Oriented Design by Alan Shalloway
>             http://www.amazon.com/o/ASIN/0201715945/
>         Refactoring: Improving the Design of Existing Code by Martin
>            Fowler
>             http://www.amazon.com/o/ASIN/0201485672/
>         Applying UML and Patterns: An Introduction to Object-Oriented
>           Analysis and Design and the Unified Process (2nd 
> Edition) by
>           Craig Larman
>            http://www.amazon.com/o/ASIN/0130925691/
>     Has anyone read the above? or there any others you suggest?
> Thank you,
> Elizabeth
> _______________________________________________
> Programming mailing list
> Programming at linuxchix.org
> http://mailman.linuxchix.org/mailman/listinfo/programming

More information about the Programming mailing list