A good source of advised best pracitce

I have just seriously reading the chapters about EJB, JDBC, Servlet and JSP, I found that there are some tricks I have used but I have not stated the reason, this book provides some short and brief reasoning for each tips to clarify why I need to do and not to do. It is very handy to me, even I explained that to my associate consultants, I don't need a long conversation. I believe the author does not mean we need to follow the best practice but hope that developers/architect can outline a set of standard/practice for the development. It is the main reason for us to read. If you have your own standard, programmer A has his/her own style, then it is hard to trace and maintain the system.

Other Reviews

• Mixed
• Has a rushed-to-press feel
• Should have been called "Review and Comparison of Java ..."
• A good choice
• A good source of advised best pracitce