Software Books

Until Mac OS X came out this book helped me with _every_ hardware and software problem that ever turned up!
Only once one of my Macs was actually beyond repair, but ever since 1999 this book really saved the day.

The iMac I purchased in July 2001 is my first home computer. I found this book at the library, then discovered it contained so much good information, that I purchased it. It sometimes has too much info for a newbie, but still it is an excellent reference. This book is the "bible of troubleshooting", and a great way to learn how your computer works. I'd say it is a "must purchase"!

The iMac I purchased in July 2001 is my first home computer. I found this book at the library, then discovered it contained so much good information, that I purchased it. It sometimes has too much info for a newbie, but still it is an excellent reference. I use 2 other books along with this one, to trouble shoot and confirm resolutions to any computer problem. This book is like the "bible of troubleshooting". I'd say it is a "must purchase"!

One of the few technical books in my library that I feel has really paid for itself, and then some. Technical books are so expensive, and most of mine sit in the bookcase collecting dust within a month or two after purchasing them. This book had saved me more money than I spent on it within the first month, and I continue to use it on a regular basis. In addition to having real and practical advice on fixing problems, Mr Landau provides advice on preventative maintenance and must-have troublshooting aids, and background on how Macs work when thre aren't any problems. I would say that this book is the most essential of those aforementioned must-have tools.

I have a lot of respect for Landau .. and he knows what he's writing about ... but this was written pre-OS X.

It's time for another edition, since OS X has a whole NEW set of problems ... including the occasional "kernel panic" (read "crash"). There is also a whole new group of compatibility issues with peripherals: printers and scanners among them.

This book is a must if you are learning BSD Unix. All the commands you'll ever use are covered in this book. This book is easy to read and explains important topics without being exhaustive (a skill some authors never learn). A great book for newbies to BSD Unix!

If you're looking for a place to start with FreeBSD (or with open soruce in general), this is really the book to get. I knew a little UNIX before I picked this up, but essentially I was a babe in the woods. This book helped me get my system up and running with clear, task-oriented discussions of all of the essentials. This doesn't go as deep as some of the other FreeBSD books out there (for that you'll probably want "Absolute BSD" by Michael Lucas), but it does tell you what you need to know to get started.

I bought the book after I had installed a broken FreeBSD 4.7 on my old AMD K6-II. Despite the few typos here and there, the book helped me figure out what mistakes I had made during my previous installation ! I thus re-installed from scratch, following page by page. In no time, the system was up and running, I was customizing my shell behavior, connecting to the internet through my cable modem (Roadrunner/Earthlink), etc...

With some extra hardware, my old AMD K6-II is now a router/firewall between my cable modem and my WinXP/Red Hat 8.0 dual-boot box without a glitch, and am planning to add a second box to my LAN and use it as a printer server too.

For those who still hesitate, this book is written in english, not in nerdish. That itself makes it stand out from all the computer litterature I've read. This book is very valuable.

Annelise: your book made my hardware firewall project feel like a walk in the park. Thank you so much !

I first tried to install FreeBSD 4.8 on my K6-2 500mhz machine using the FreeBSD Handbook as a guide. While this book (the Handbook) is the standard for reference on the subject, it doesn't really explain it to a newbie's needs (even someone coming from Linux). My first attempts failed. I bought Annelise's book and was able to get 4.8 up and running following her suggestions. Though my copy came with a CD of FreeBSD 4.7, I had already burned ISO images of 4.8. The processes detailed in the book applied equally well. My only complaint would be that the book needs updating to reflect areas that a lot of people (most people) are interested in these days: burning music to CD - especially ATAPI CD devices, and USB mass storage devices. Both could be covered by a chapter on how to use SCSI emulation. I still give it 5 stars.

I had been getting fed up with using Windows and wanted to learn a new operating system. I bought Anderson's book and installed FreeBSD 4.6 on an extra hard drive in my computer. The book covers a broad range of topics and I found it very helpful during the installation process. The first 10 chapters are great. I started to get annoyed with Chapter 12 on connecting to the internet. I used PPP and something kept going wrong. I still do not know what it was but the errors I got were endless. The chapters little sidenotes on troubeshooting were of no help and I eventually gave up. Then I tried to install the printer daemon and also recieved errors. I followed the book as best I could and eventually gave up and moved on. Chapter 14 on the X window system is great. Other than the printer and PPP problems (which could have just been my misunderstanding of the book), I would recommend this book to someone else

I bought three books to teach myself how to produce DVDs. The Erica Sadun book is for advanced users and was not helpful to me. The Bob LeVitus "Little iDVD Book" is probably one of the most poorly organized and edited books I've ever come across on any subject.

Pogue's "Missing Manual", on the other hand, is comprehensive, clear and well-organized. I've produced about half a dozen DVDs since reading (and re-reading) Pogue's book and it clearly made a huge difference in what I was able to construct using iDVD.

In my opinion, this is the only book you need to read to learn how to produce movies using iDVD.

Beyond teaching readers to work with iDVD, Pogue also offers loads of helpful suggestions about editing in general. This book is outstanding.

I love this book! I was ready to give up trying to use iMovie because of a small glitch that was incurring. After browsing thru the book the very first time I opened it, I came across the trouble I was having with iMovie. Mr. Pogue directed me to the correct settings and I am now having a great time editing my DV movies.

I would highly recommend this book to anyone attempting to use iMovie. There is so much more to this program than Apple addresses in the help file. Mr. Pogue's writing is concise but not out of reach for the average Mac user.

I have many books by Mr. Pogue and I would recommend any of them if you are stumped and need a well explained how-to-manuel.

Can it get any simpler !! ha ha ha ha ha
I found this book to be extremely informative and easy to understand (especially since i am yet to purchace a mac and digital video cammera ).. I will have no hesitation now to go out and purchase a Mac and a Digital cammera .. and feel confident making my first feature film or "Home Movie " LOL

It's OK. It has about the same amount of material as the "iMovie 2 for Macintosh Visual Quickstart Guide" - The missing manual is fatter because it contains additional stories and things that a reader might find amusing, but that are not particular relevant to the topic. The section on movie making basics is very good. For an expanded view see "The Five C's of Cinematography". I thought I would find more information in this book since it is fatter than in the VQG, but it ended up that they are about even in content.

First I have to give props to David Pogue and his Missing Manual series. As a bookseller and computer geek I've long favored the Dummies books as the best entry-level source for third-party information on software. However, O'Reilly made a smart move when they turned their attention on that market and grabbed Dummies standby Pogue to headline the new series. The Missing Manuals (and their mutant-dogcow mascot) are a credit to O'Reilly and a must-have... assuming, that is, that they cover the program you need. The series is still too small, but I'm sure it won't stay that way.

Now, to the book itself. If you need to do something with iMovie, it's in there. That pretty much covers what I need to say in this review, but it doesn't cover everything the book has to offer. Remember back in the 80s when the Mac made desktop publishing a reality, only to unleash a torrent of wretchedly amateurish graphic design? Well, Pogue spends much of the first couple of chapters attempting to prevent that from happening. This book starts off with a very basic primer on video production and how to use your equipment -- assumed to be a typical consumer-grade MiniDV camcorder, but it covers other options as well, particularly video bridges and the like.

The meat of the book discusses iMovie 2's capabilities, including discussions of its weaknesses and how to work around them. Effects, titles, and transitions are discussed in detail, including some useful information on crossfades (never fade straight to black -- instead, you want a black stillframe). Conversion to other formats is also an issue, and a significant part of the book discusses postproduction using QuickTime Pro. Directions are given for converting your work for DVD or VCD as well.

The issue I have with the book is largely its focus on iMovie in MacOS Classic, and the bugs that are present in that version that might not be in the OS X version. Screenshots all come from 9.x, with the only Aqua material being the interface of iMovie itself. I don't mark down for this since the program operates more or less the same, but an inexperienced user may have trouble. (I might note as well that the book works just as well for iMovie 3, which has a superficially different interface but handles more or less identically.)

So, yeah. If you're doing video production on iMovie, this is the book to get, hands down.

This in-depth look into transaction processing provides a wonderful place to start when considering implementation in your application(s). Cover-to-cover, this is an EXTREMELY easy read and doesn't try to be "fancy" or use complicated wording as many other books on the topic do.

Before reading any other transaction books or jumping into API document, this is a MUST MUST MUST MUST read. When developing an application that has transaction support, this is wonderful as a reference in order to include data in presentations, summaries, position papers, internal documentation, etc.

No only will this benefit a general developer, but also benefit people not in the development environment. This allows for clarification of communication between departments without going into API-specific implementation details.

This book is excelent for who want to deep his knowledge in TP. Is very practical with many examples and tips. Funthermore include examples of of transacctions for commercials TP like a MTS (COM + today), Tuxedo, CICS, etc.
Is a book very very recommendable.
bye.

The title of this review is a quote from the book and it summarizes it very nicely. Indeed, the book provides a great deal of information in such a small volume, but many of the things that would have been nice to have are missing and many are just skimmed over.

The best chapters of the book explain in very simple words the principles of transaction logging (along with recovery from a failure), two-phase locking and two-phase commit.

The chapter on transactional communications is not as thorough as the just mentioned ones and pays most attention to transactional message queueing rather than synchronous RPC and peer-to-peer. On top of that, message queues are just transactional, period. No attention is paid to the message queues specifics.

The chapter on transaction processing monitors considers only the three-tier environment with presentation, workflow and transaction tiers.

Other problems ?

The whole chapter with an overview of the existing transaction processing software was useless. You see, product Foo has features A and B, and product Bar has features C and D, so what ? As you read it, certain architecture similarities show through, but it's up to you to analyze it, the book gives no cross-product comparison, no analysis, just a list of acronyms.

Samples in Cobol (duh !) or tangled C-like code. The pictures are less than perfect.

But the biggest problem to me was certainly the lack of real-life information. Specifically, I would better be interested in interaction between transactional and non-transactional systems. An acknowledgement of databases and message queues being the only transactional systems (or not) and the implications of that. Two-phase commit in heterogeneous environment. And so on.

A great introductory book.

Transaction processing is a daunting topic, and this is one of the few books that provides the basics in a clear, understandable manner without overwhelming the reader. Most of the book is focused solely on transaction processing, but it touches on queuing as well, which makes it the ideal first book for anyone who is seeking details that extend beyond pure TP.

I like the way that the authors use real products to reinforce key points made throughout the book. While some of the products are no longer mainstream (indeed, some were never mainstream), the fact that real world implementations are used makes the information realistic. If you are using CICS, MQSeries, Tuxedo or similar products this book will have even more value. I also like the way difficult topics, such as locking, high availability and database recovery are given entire chapters because these topics need to be thoroughly understood in order to completely understand transaction processing.

After reading this book you will be armed with sufficient knowledge to make intelligent choices in selecting the right approach for transaction processing in a system design, or to understand the nuts and bolts of any TPM that you are supporting. I also agree with Cem Kaner's earlier comments that this book is an ideal resource for software test professionals who need to understand the entire environment that they will be testing. If you want to go deeper into TP, I recommend "Transactional Information Systems: Theory, Algorithms, and the Practice of Concurrency Control" by Gerhard Weikum and Gottfried Vossen, which drills much further down into the details of both transaction processing and queuing systems.

This book was written in 1997 which is often considered ancient in "Internet-years" but it is still very relevant because it focuses on fundamental principles of transaction processing (TP) rather than the latest whiz-bang technologies that optimize TP.

For those of you who aren't TP experts, a transaction is a computer operation that meets the ACID test. ACID here stands for:

Atomic - the steps that comprise transaction succeed or fail as one, there is no partial success.

Consistent - the internal data structures of the system(s) remain consistent with business rules.

Isolated - the data read or manipulated by the transaction is not altered during the duration of the transaction's execution.

Durable - the results of the transaction are persisted

Why does this matter to the system user or stakeholder? The canonical example is that of the ATM machine (or the "handy bank" if you're Australian). When you withdrawl money from an ATM, it has to go out and validate you have enough funds to meet the withdrawl, reserve those funds, and dispense cash - all within the same transaction. If the ATM failed after your bank account had been debited but before you'd gotten your money, you'd be very upset; conversely if the cash was dispensed but the debit procedure failed, the bank would be very upset. Ted provides very amusing analogy for this using a wedding ceremony but you can read that in his book.

There's a whole lot more to transaction processing beyond ACID and the ATM example, including two-phase commit (TPC), high-availability, massive concurrency, and crash recovery. To find out about all of these topics, read the book. One thing to remember though is that most application developers will never have to deal with the extremely complex details of providing a working and robust transaction management implementation, but like any technology it's important to understand the technology's fundamental principles and mechanics to effectively use it.

The book itself is extremely dense. The content of the book is "only" 324 pages long but covers a large amount of ground in a good amount of detail. Definitely read in a quiet place free of interruptions with a strong cup of coffee.

One shortcoming of the book is that it was written in 1997 so it doesn't cover TP implementations in Java (e.g. JTA, EJBs, etc.) but it was nice to finally find out what the heck IBM's CICS and IMS products are.

Interestingly enough, I have never had to deal with complex transaction processing (i.e. two-phase commit) in my short IBM career. This is probably because I've worked on business-to-consumer (B2C) applications where only one data source is involved rather than a business-to-business system where multiple data sources are involved. I'll have to ask the B2B guys if they get heavy into two-phase commit or if it's not an issue.

The reason I read this book is because I've always been a bit mystified by Enterprise JavaBeans (EJBs). When I joined IBM, I knew the word, but I was not familiar with such topics as object-relational persistence, object remoting, and transaction processing, so to me EJBs were simply things that took four classes/interfaces to do what I could do in one simple POJO. Ted Neward, in a very interesting web interview on the Serverside.com mentioned that he used to think EJBs were completely worthless, but during the process of writing Effective Enterprise Java came to realize that they were not worthless but rather over-marketed. He said that they should have been called Transactional JavaBeans rather than Enterprise JavaBeans because transactions are what EJBs did very well. So, hearing this from Ted I decided to read a book on fundamentals of transaction processing, so that I could understand EJBs better. Now that I've read all about TP principles, I pick Richard Monson-Haefel's book again, and all of a sudden EJBs start to make a lot more sense.

I finally picked up this book last year and throughoughly enjoyed it. I keep referring to it because the examples build up to the point of qualified proof of concept. The examples also are different enough from the other ones that are easy to find with Google, so between the two you get a complete view of the vulnerable issue.

The book's title should be obvious enough; this is NOT a book of defenses. However, if you understand these attacks you will be better equiped to deal with them when they happen. This book is no replacement for hands-on training in person with a qualified instructor such as at the SANS Institute, but it is an excellent supplement.

Its a great place to start...and works its way through some pretty indepth concepts. The great part is that for the beginner it is step by step....and they tell you were to download everything you will need. Anyways loved it, read it twice.

I have been around the software industry now for almost 20 years and every now and then I find a book where I learn exciting things, this is one of those books. It reminds me of the early days of low level Windows programming but with very up to date information on the OS and how to apply it. The book is obviously designed to attract hackers - both black and white hats - however it does do a good job diving on the internals of the Posix and Windows subsystems. If you like low level stuff this book is for you.

Not an easy read if you're not already familiar with programming and operating system concepts, but then if you are an IT security professional you'd better be, and the book explains why.

I read Rootkits: Subverting the Windows Kernel last year, but waited until I read Joseph Kong's Designing BSD Rootkits before reviewing both books. In a head-to-head comparison, I thought Kong's book was easier to comprehend and directly covered the key techniques I wanted to see. If I could give this book 4 1/2 stars I would, but Amazon doesn't allow that luxury.

Hoglund and Butler should be commended for writing this book. It really does assemble the parts (meaning techniques and code) necessary to implement a Windows rootkit, at least prior to Windows Vista. My only concern is that, at times, the authors are not as clear as I hoped they might be. This is probably due to the fact that they are two of the best rootkit writers on the planet, so they probably do not remember what it was like to not understand "hooking" and other techniques.

In some ways Rootkits is probably a book best suited for other experts (like many who wrote reviews here). That leaves beginners (like myself) wishing for a little more foundation or direct language prior to reading about implementation tricks.

One of the greatest strengths of this book, however, is the degree to which it exposes the internal workings of Windows. For greatest effect it's probably worth reading Microsoft Windows Internals, Fourth Edition by Russinovich and Solomon first.

Note that although I found the direct approach of the BSD rootkits book better for my learning style, this book by Hoglund and Butler is deeper in several areas. In fact, those who liked the BSD rootkits book would do well to read its Windows counterpart to learn tricks from Hoglund and Butler.

this book is an excellent information source for both professionals in need for a reference on a db2 topic/ students trying to get into db2 / certification hunters interested in ibm 730 exam db2 administrator for V9 .
very well written.

if you looking for a db2 beginners book...its a right choice...even if you are a exp. dba, this book can come handy anytime for any reference or as a guide..

If you are new to DB2 this is the book you need.
It covers all the basic information you need to start working with db2, in a easy way.
If you also want to get certified get the DBA guide or one of Sander's book, and you are all set to go.

This is an excellent book for DB2 if you are a beginner or even an intermediate skilled user. This book covers not only DB2 9, it covers DB2 9.5 and the facts that pertain only to v9.5 are duly bulleted/annotated with the version number. This book treats DB2 from a DBA point of view so the SQL examples are pretty basic if you are a hardcore SQL programmer. If you are looking only for SQL programming for DB2 this is not the book to buy. But for an administrator, this is one of the best reference books on the desk. Since this book has lot of visual examples, you see what the authors are talking about rather than forming a mental image. Also, it covers XML/XQuery in DB2 in detail. Moreover, this book is an excellent reference if you are taking certification in DB2.
If you are on the lookout for the one book that will kickstart your DB2 career; this is the one.

If you have to own one DB2 book (Linux,Unix,Windows) , buy this one. Usually I end up buying 2 books. The first being a book being very visual and easy to read but lacking any real detail and practical knowledge. The second book is usually a scary developers guide which is extremely thorough but requires a PHD to read it, or you end up using it as a reference.

This book hits dead on!! Incredibly easy to read with examples and visuals that make understanding difficult concepts easy, but its encompasses every important concept in DB2 with plenty of detail. I love this book and recommend it to anyone looking for the DB2 book to buy. Of course there are times you will need to access DB2 Info Center when you need very specific detail, but this book will provide you on the right track and explain how you got there perfectly. Hats off to the authors of this one.

This book is not only good for project managers but also an excellent read for developers. In the real world it is not uncommon that developers would confront a manager who likes to micromanage and everything the developers do have to be conform to something really bureaucracy and with little or no business sense or tech sense. In this book, the value of APM is well articulated in concise sentences. These sentences can be powerful tool when it is necessary for R&D people to discuss/argue with a manager about things like project plan/report, etc. There is also practical method of APM. I find this book very articulate and concise. Highly recommended.

This book is a thoroughly enjoyable read, from the emphasis on principles, the excellent job navigating the difficult territory of the line between prescribed process and anarchy, and the stages a team goes through as it embraces an agile style of development. I even thought that the hypothetical story added a nice element of repetition to each section that helped drive home the main points.

The one thing I would've liked was for this book to get off the fence and decide to be software-related. Almost every example is software related (except for the basketball analogy that got beaten to death...), but it goes out of the way not to specify software practices because this is about arbitrary project management. The book's in the "Agile Software Development Series" and the author is primarily a software consultant. I'd prefer it stuck to software rather than trying to go for broader appeal because there were several practice areas where detail was elided on that basis and could've really helped make the practices more concrete.

Also, it would've been nice to have a little grid mapping up common-day software development methodologies like Scrum, XP, FDD, and DSDM against the practices in the book. I tried to do it in my head, but once you get past 5x5, it's something that should've been provided.

I picked up Agile Project Management because I haven't done any agile projects in a while and wanted to update my knowledge to help with an upcoming project. I found the book a good combination of theory and practical activities that a project manager can use in an agile project. The book steps through each of the processes, explains the theory, then steps through tools that can be used for that process. I recommend this book for anyone new to agile project management, including experienced project managers looking to expand their toolkit.

This book is well-written and provides both a good explanation of agile software development and insights into how to manage such a project. My disappointment comes from fact that Highsmith emphasizes that one has to find the right people in order to succeed with this kind of project, and doesn't provide much info about how to identify the right people or how to train people with potential to work this way. Given the emphasis on the importance of the right team, more space in the book should be devoted to that aspect of management.

As someone who has managed large custom software projects and programs for 20 years, I was concerned that applying Agile to project management would simply mean burndown charts and the like. What I found in Highsmith's book is a perceptive understanding of how people think, feel and actually work on projects. Approaches that take human behavior into account, in my experience, are far more successful than those that don't.

The concepts covered here, if really absorbed and understood, can benefit any project. I found Chapter 7 to be the most valuable for my current product development team, and ordered copies of the book for all my managers.

The book never arrived at 3 weeks, so canceled the order and hope the charge is reversed on my card. Woody's books was nice about the problem and sent me a $5 check to aid in buying the book at a higher cost in a local book store.

This is a fantastic book for the newly-diagnosed breast cancer patient. It was given to my by my surgeon's office. It does a great job explaining things on a level that the average person can understand. It also has great diagrams, lists of questions to ask your medical team, glossary of terms, websites to check out and comments from breast cancer survivors and/or significant others of survivors. I highly recommend this book.

We give this book to surgeons in our area to distribute to women diagnosed with breast cancer. Before purchasing it, we had a group of 4 breast cancer survivors review and rate 3 separate books on breast cancer. This book "won" hands down, based on numerous criteria -- everything from its explanation of breast cancer treatments, to its index and glossary, to its discussion of life after cancer. It is clear and easy to read, provides comprehensive information on types of breast cancer and corresponding treatment alternatives, has wonderful graphics and photos, and provides interesting anecdotal stories of actual patients in its sidebar. Highly recommended!

I was introduced to this book at work and am now giving it to women newly diagnosed with breast cancer. I am on oncology certified nurse in the radiation oncology department of my cancer center. In January 2007 I also became our Breast Cancer Patient Navigator. I find this book gets excellent reviews from patients and their families alike. It is a great source of information, covering all the topics from diagnosis to living life 'after cancer'. I only wish I would have had this book when I was on my personal breast cancer journey! I highly recommend this book for someone newly diagnosed with breast cancer.

"Many experts believe that Herceptin represents the future direction of breast cancer drugs, because it targets a particular protein on the cancer cell, rather than attacking all cells at random. As research progresses, scientist hope to make all anti-cancer drugs as specific as possible." ~ pg. 97

Designed to compliment the book, the DVD provides an environment of understanding with explanations for all the procedures and various situations that will occur after a diagnosis. New treatments like Immunotherapy are discussed and there is an extensive resource section with additional CD options, including a CD-ROM program that is an interactive guide to treatment.

Helpful up-to-date information about why you may not need a mastectomy and only a lumpectomy is encouraging and gives hope. Radiation and Chemo is also discussed in detail. Throughout both the DVD and book, women tell their stories and that gives a sense of the range of experience. There are over 150 color photographs and graphics to illustrate important points.

A variety of questions are given in each section so you know what to ask your doctor. The stages of breast cancer are given so you know exactly what your doctor is talking about. The main sections include:

Facing Breast Cancer - Your feelings, support groups, healthcare teams and overview of treatment options.

Breast Cancer Basics - Types of Breast Cancer

Diagnosis and Staging - Tumor Testing, the Pathology Report, Additional Tests, How Stage is Determined

Surgery - Reconstruction, Lumpectomy and Mastectomy options, Lymph Nodes

Reconstruction - Choosing a Plastic Surgeon, External and Internal Options

Radiation Therapy - How treatment is given, Brachytherapy

Chemotherapy - Side Effects, Common Chemotherapy Drugs

Hormone Therapy - How Treatment is Given, Who should be Treated, Side Effects

Immunotherapy - Future Therapies and Herceptin

Clinical Trials - Participation Ideas and getting the newest treatments...

Life after Cancer - Emotional Recovery, Physical Recovery

The Guide for Your Partner is a special section your partner can read. If possible, watching the DVD together would be ideal because it explains all the basics in the book.

Be a Survivor is an excellent resource because it gives you all the questions you need to ask and answers a number of pertinent questions any woman will be asking the moment she is diagnosed.

Vladimir Lange, MD is one of the most respected doctors in this field of study and this book came into being after his own wife was diagnosed with breast cancer.

~The Rebecca Review

I can also recommend "Reconstructing Natalie" by Laura Jensen Walker.

This is a readable, practical, and deep book. It's one of those books which teaches or refreshes Java and OO theory and practice as you read. I am also reading it for pleasure!

This is a great book. It is directed at users of JUnit, the Java unit testing framework. But in my mind the book gives sound advice for solving your programming problems in general, not just for Java or JUnit testing. It stresses the importance of unit testing, programming to interfaces instead of implementations and just simple common sense. The author is clearly passionate about his field and extremely experiences. The combination of enthusiasm and experience comes through on every page.

This review also appears on StickyMinds at http://www.stickyminds.com/s.asp?F=S767_BOOK_4

JUnit Recipes is a comprehensive tome of practical methods and techniques for the opensource JUnit tool to develop automated unit-tests for Java/J2EE applications. The book is split into four parts: Building Blocks, Testing J2EE, Additional JUnit Techniques, and Appendices. The Building Blocks cover the basics of using JUnit to create basic tests, organize and manage test suites and test data, running JUnit tests and reporting the results. It even includes a section on troubleshooting. Testing J2EE covers XML, JDBC, EJB, web components (including JSPs), and J2EE applications. Additional techniques include testing some well known design patterns, using JUnit add-ons and JUnit libraries (like GSBase). The Appendices include complete solutions (including code of course), some short and sweet essays on testing, and a modest recommended reading list.

The organization of the book flows very logically and the writing style is very clear and easy to follow. Along the way many insights into important design principles and testing techniques are revealed: the reader will learn about the "Hollywood principle", the Open-Closed principle, design patterns, POJOs, Mock Objects, Private and Parameterized Test-Cases, Abstract Test-Cases, Self-Shunts, and Spys. The book's coverage is very comprehensive and touches on many other popular Java/Enterprise projects and frameworks such as Struts, JBOSS, Prevayler, XDoclet, Tomcat, XPath, XMLUnit, HTTPUnit, Ant, Jakarta, and others.

Even though JUnit is often associated with "Agile" development and much of the wisdom apparent in the book applies to agile Java development, the book is useful to any Java developer on any Java project (agile or otherwise). The book also goes into considerable detail, with working code examples, to spell out exactly how to perform and apply the techniques it describes.

The book's primary audience is Java developers. Java Tester's will still find some good nuggets of information but it's quite clear that Java programmers and developers are the target audience. This isn't some high-level theoretical book mostly of concepts and ideas. This is an imminently pragmatic guide that not only conveys a great deal of highly practical wisdom but also clearly and comprehensively walks you through the explanations and the code to accomplish and apply the techniques it describes. The book is also not a "How To" for coming up-to-speed on setting up and running JUnit.

Another book from the same publisher, "JUnit in Action" is a great overview on learning more about the basics of running and using JUnit and on using JUnit to tackle a number of basic challenges with unit-testing Java and J2EE code. JUnit Recipes has some overlapping material but pretty much "picks up" where "JUnit in Action" leaves off, and JUnit Recipes goes into much more breadth and depth of coverage of JUnit methods, practices and techniques and use with other Java projects and frameworks.

I would say JUnit Recipes should probably be required reading for anyone attempting to use Java, J2EE and JUnit in the real-world.

This isn't necessarily the best introduction for absolute beginners (I would recommend /Pragmatic Unit Testing/ for that), but it is required reading for server-side Java, as most other reviewers have pointed out. But it's more than that--it's one of those rare computer books that transcends its subject matter. Why? Because it can make you a better programmer. While some of the credit can rightly be given to unit testing and Test-Driven Development in general, Rainsberger's book makes you /see/ better ways to write and refactor your code. The breadth and depth of examples is astonishing--he convincingly shatters "but it's too hard to test that" arguments with well-researched, non-trivial examples. In fact, I'd say that this is almost a better J2EE tutorial than most books about J2EE proper.

I'm withholding a star for one reason: the book doesn't cover GUI testing tools like Jemmy, JFCUnit, or Abbot/Costello. These JUnit extensions are ripe for a book with this depth; it's just too bad that this couldn't be that book. Other than that, I find that I turn to Rainsberger's book far more often than any other testing book or online reference.

Rainsberger does a very good job of detailing the techniques to unit test difficult code; including xml, ejb, servlets, jsps etc.

OK... we have all heard jQuery is the in library from someone somewhere. Yet, it does so much and it does it differently. How do we shift gears and get into the library. This book is well thought out and covers the basics and beyond in a very friendly fashion. I want more details than can be contained in a book of this size, lol. We all want the books to cost less and contain more. But one of the key ways I rate books is how well did the concepts of the book sink into my brain on the first read, and how often do I take the book off the shelf for 'instant refreshers'. This book is top quality on both those areas.
(FYI... by way of reference I am the author of ColdFusion 8 Developer Tutorial )

This book is great. It teaches jQuery very effectively and in a manner that all people can understand. I highly recommend it to anyone needing/wanting to learn jQuery.

very complete overview of the topic with well layed out examples. The reference book is a better long term value.

I call this the second javascript book that you will ever need because you will first need some background and understanding in javascript such as from: Simply JavaScript. However, once you begin working with Javascript you'll find yourself wishing for an easier way to accomplish numerous tedious tasks. The solution is jQuery an open source javascript library that is supported by a sharp team of developers. Jquery uses an OOPS approach to many common tasks and provides a framework to accomplish in 1 or 2 lines of code what would take dozens using javascript alone.

Although Jquery is pretty straightforward the online forums and documentation aren't always clear and directions for someone starting out in Jquery aren't the best. That is why I bought this book and it has been an incredible help to me by giving me a structured, ordered and organized explanation of what Jquery can do. You'll find yourself savings plenty of time with it and expand your javascript capabilities exponentially.

I've used JavaScript for 9 years and have hated the way it needs to be developed differently for different browsers. And there are the little gotchas that take way too long to run down in forums. Enter jQuery.

The jQuery JavaScript library takes the pain out of using JavaScript. It handles the browsers and leaves us free to simply add functionality to websites in a logical and consistent way. Learning jQuery teaches jQuery in a best practices manner without preaching and makes adding interactivity to sites reasonable. I don't have to throw in the towel on JavaScript and resort to page the reloads that a server side solution would demand.

I can't imagine a better introduction to jQuery. Learning jQuery is well thought out and paced. Concepts are presented in increasing complexity with plenty of excellent examples. Working through this book gave me a solid foundation in jQuery and the confidence to experiment with my own needs. Few programming books are so well written. The example code is high quality, too with few typos or errors.