Title: RE: EJB naming conventions?
If you are an advanced developer, I would not buy Coad's book.  Unfortunately, there is a real lack of advanced java design books.  There are a few niche books worth reading (like Doug Lea's book on concurrency).  I have taken to finding non java books in the field I am interested in, which greatly increases my chances of finding something worth reading.  For example, I'd read In Search of Clusters for clustering,  Jim Gray's Transaction Processing for TP design, Queueing Networks and Markov Chains for asynchronous programming and issues, etc.
 
Erik
-- 
Erik Huddleston, [EMAIL PROTECTED]
Chief Architect, eCustomers.com
Microsoft Java MVP
-----Original Message-----
From: A mailing list for Enterprise JavaBeans development [mailto:[EMAIL PROTECTED]]On Behalf Of Javier Borrajo
Sent: Wednesday, October 20, 1999 2:34 PM
To: [EMAIL PROTECTED]
Subject: Re: EJB naming conventions?

Actually it has 3.5 stars which is quite good for a book with 31 reviewers.  If you read the comments, it is mostly either 1-2 stars or 5 stars.  This usually indicates that the intended audience was not clearly conveyed.  Almost all the 1-2 stars were from people who were complaining, "but I already know this...."  As I recall from the introduction, it is geared toward beginning to intermediate developers (those who know the syntax).
I have not read Coad's book, I consider myself "advanced developer", so do I understand
I should not buy it?
As to your recommendation, Coad's book is an excellent book on design _not_ design patterns (ala PLOP or GoF).  Patterns in Java is a good book (well, the first one is at least), but covers a different set of information.  Coad's book is more like Java In Practice or Java 2 Performance and Design Idioms.
Erik (whose read just about every book on Java in print... :-)  )
 
I did not really pretend to compare both books, they cover different ground,
I had not read Coad's book, and I like Grand's book.
 
Regards
 
    Javier (reads a lot, too ;-))
(BTW, I like what Microsoft is doing with XML/SOAP/RDS/ADO/HTC/HTA/... and other asorted TLCs)

As I recall, Peter Coad had a nice summary of the advantages of using the "I" prefix for interfaces in Java Design:

http://www.amazon.com/exec/obidos/ASIN/0139111816/qid=940430526/sr=1-15/002-0300451-4975441

From what I see at Amazon this book seems to have really terrible reviews...
I like "Patterns in Java" by Mark Grand
 
    Javier

Reply via email to