Most Helpful Customer Reviews
|
|
3 of 3 people found the following review helpful:
4.0 out of 5 stars
Gives good ideas to accelerate development, 27 May 2005
The book introduces many tools which might be useful during automation the build, installation, and monitoring of a large-size java application. (Ant, JUnit, Groovy, CruiseControl, NSIS, Java Web Start, XFD build monitor, Unix scripting, Ruby, log4j, Jetty)The description of these tools is not deep at all, the book places more emphasis on covering the whole process from the first build to the customer support, taking all automation options used by professional software developer companies. The text is easy to understand. The only reason why I gave four stars is the poor book binding: pages start falling very soon.
|
|
|
1 of 1 people found the following review helpful:
3.0 out of 5 stars
Good philosophy and overview, pity it's so Java-oriented, 3 Feb 2009
The philosophy of this book is one that I agree with completely. That is, if you want a reproducible, traceable and maintainable system for building and releasing your software, then automate the processes involved. The larger the project, the more time and money you will save.
So, in terms of philosophy, I'm a big fan of this book. I particularly like the extreme feedback devices for making the status of builds very visible. That visibility tends to encourage people to follow good practices and write working software, probably more than anything else. I also like the explanations of starting with a process started interactively, to a scheduled process, to a continuous/triggered process. Similarly, the discussion of release builds being separate from development builds is good.
However, this book does have limitations. The (easily missed) sub-title "How to Build, Deploy and Monitor Java Applications" warns the reader of the main one. This book really is aimed at people working with Java and tools that are primarily aimed at Java developers. Whilst tools such as Ant and Cruise Control (and their derivatives) can be used for non-Java projects, Java is their key target. Similarly, this book refers to CVS in its examples. Unfortunately, the choice of version control software can make a significant difference to how build and releases processes are implemented (in particular the use of labels vs. tag directories). Whether done in an update to this book, or whether it is done in a separate book, it would be good to include more about building for other languages (e.g. C++), more about non-UNIX operating systems (e.g. Windows), using other version control systems (Subversion, PVCS, SourceSafe etc), using tools other than Ant and Cruise Control (including scripting languages, whether batch-files on Windows, Python or other scripts) etc. The problem then would be that the book would be two or three times as long, at which point many people might decide it is too "heavy" to read. Tricky.
So, I love the philosophy. I like the overview of what people should be doing. I find the descriptions of the tools used adequate. But I would have liked to see wider coverage beyond the Java, Ant, Cruise Control etc environment discussed.
|
|
|
1 of 1 people found the following review helpful:
5.0 out of 5 stars
Enough information to start implementing good practices, not overwhelming, 25 Jan 2009
I bought this book over 3 years ago and still use it today, even though I have 100's of books on software development and software testing. Like all the pragmatic programmer books I own (I have about 6) it's clear, direct, and helpful. These books are good value for money and portable.
Books such as Java Power Tools from O'Reilly are complementary (covering a range of newer tools) and the Manning JUnit Recipes & JUnit in Action cover JUnit in great breadth and depth.
|
|
|
Most Recent Customer Reviews
|