The book explains the benefits of the technologies/tools it describes (JUnit, Cactus, Ant, HTTPUnit, etc) and explains how to use them in an easy to understand manner and gives some good examples. I feel so much happier now when I commit my code to CVS having written tests to ensure all is good.
Using Ant to do all the hard work for you is just amazing! The code examples in the book can all be download from Rick's website and when ever I have emailed Rick and Nicholas with any questions they have sent me very helpful replies.
I have to say this has been one of the best presents I have received!
This book has helped to make my programming much easier, quicker and solid. Most of the ideas in the book are common sense and you end up wondering why you never did these things before!
I have to say that I absolutely love your book!!
Although I'm not all that familiar with J2EE the concepts presented throughout the book are very helpful. If you understand a little bit of J2EE or even the concepts, I think that you can follow on.
I really enjoyed this book. The title is a bit unfortunate, as while it
summarizes XP development concepts, its not the main focus of the book.
Perhaps a better title would be "Integrating & Automating Multi-Component
Software Project Building & Testing using Ant, JUnit, Cactus, etc." but
this is a bit hard to fit on the spine of the book.
From a development management standpoint, this has eliminated (or at least
focussed) about a hundred water-cooler discussions about how to go about
putting together the build & test system. And for the meeker developers,
it gives them a quick tutorial on what the hell everyone else is
jabbering on about.
If you decide to comment on the book, can you state what your party affiliation is..., i.e., XPer or not.
If you are not an XPer, can you state the likely hood of looking into XP after reading this book.
I am just curious.
BTW This post stuff needs a spell checker. Its making me look bad!
I have been developing/deploying code for a few years, well before XP entered the jargon. I like your book as it describes the tools well without getting into the *preach* mode most XP/XPer's books get into. The XP methodology would be better served if there are more books like the one you have written.
Originally posted by Ravi Veeraghanta:
True,it's not necessary to spend years in design [...].
But a good design gives you a focus and direction which is invaluable.
Most XPer's I have dealt with seem to equate it with a religon. It's like, "Thou shalt use this eXtremly Painful methodology or you will burn in hell" or something like that.
So some XP people see their job as “selling” XP to a cold audience.
"This book is the first of its kind, covering topics that haven't been explored this directly anywhere. It does a remarkable job, covering not just the tools but the philosophy behind good unit tests and frequent, automated builds...." ... ... "The philosophy behind this material is modern and forward thinking. ... (The book has the ) potential to make you a better programmer and better able to deliver higher-quality code on a shorter timeline. "
"...This book is a fine introduction to a whole bunch of really useful tools to boost your Java and especially J2EE programming.... This book was almost too useful to review. ... If you want to get up to speed quickly and practically on a load of useful, powerful, tools - get this book. Everyone I've shown it to has wanted their own copy ... "
"This book should appeal to XPers and non-XPers alike who recognize that automated testing and continuous integration are good things for any project." ... ... "The book is a good introduction for the uninitiated and a valuable reference for those plying their trade with these tools. Don't miss an opportunity to easily automate your Java project and spend more time delivering business value!"
Originally posted by Ravi Veeraghanta:
-Introduce tools like Ant/make,Junit,Cactus. Developers like tools that make their job easier. It's also easier to get a buy-in when you can demonstrate something concrete and get immediate
-Remember most organisations/people do not "embrace change" easily so don't go in and try to demolish existing practices.
-When you are suggesting a new tool/new approach list out all the practical benefits that can be obtained. Do not say it worked in xyz co., or that this is the latest way things are done.
-Some aspects of XP may be counter-intutive but people do see reason. Be patient and ask people to give it a try for a small amount of time.
-And remember XP is only a methodology. It's not an end but a means to an end.