5 comments about Designing for Interaction: Creating Smart Applications and Clever Devices (VOICES).

1. Designing for Interaction: Creating Smart Applications and Clever Devices (VOICES) is good book for me.
   I learn digital medea design so it is good for me.
   What is interation design?
   I don't know well now.
   But I will study more.
   I want be a good designer in this field.
   Be ambicious!



2. The useful information in this book could be condensed into a 10 page article. The rest of the book is just irrelevant or uninformative photos, self evident ideas, and short interviews with designers. There is knowledge for designers between the covers - but not a bookload. This book tells you how to go about researching for design, but doesn't tell you anything about what other researchers have learned.
   If you are looking for a book that helps you decide how to position the controls and labels on your latest widget, this isn't it.



3. I am an aspiring interaction designer and this book by Dan Saffer really nails it for me in terms of laying down a coherent and well-written overview and framework.
   
   This book is essential to the interaction design community in that it defines clearly what interaction design is (and is not) in this early stage of this new industry.
   
   It is also essential reading for all beginning or aspiring interaction designers.



4. This book reads like the author sat down on a weekend afternoon, typed out a draft and simply published it. The text is basically a sequence of obvious statements. In fact, this book is so bad I don't want to waste many words reviewing it. So I am going to randomly select 4 sentences from this book:
   
   - Most applications and devices that interaction designers design have some sort of visible controls for the user to use to manipulate the features of the product. pg 136
   - Designers should be open and nonjudgemental and should not assume that they know the answer beforehand. pg 80
   - It is more important now than ever before that our digital tools have the characteristics of good interaction design baked into them. pg 203
   - The system needs an assortment of responses to deal with a range of situations. pg 38
   
   Believe me, I haven't chosen these lines consciously - I closed my eyes, turned to some page, put my finger down and typed the sentence my finger landed on. The whole book is filled with such drivel.
   
   I wish I could give this item a rating of zero. Spend your money elsewhere.



5. This book is helping me to understand how i need to start to design interactivity for Digital Television. A must-have.

5 comments about EJB 3 in Action.

1. This is THE BOOK for EJB 3.0. Covers everything about EJB 3.0.
   Also outlines migration from EJB 2 and integration with ORM tools.
   It's a highly organized and well written book.



2. I have been working with Enterprise Javabeans for many years. This really is by far the best resource to date on Enterprise Javabeans. One of the many strengths of this book is to show how the Springframework blends into the EJB framework. I have had a lot of success in blending these frameworks. The authors really believe in the EJB framework unlike another major author of EJB books.



3. This is my third book on EJB 3.0 and in my opinion the best one. I'd recommend it to anyone who wants to learn Enterprise Java Beans and Java Persistence API.



4. I was not that enthusiastic about EJB at all during the EJB 2 era. Then I knew about the EJB 3 specifications and that made me read this book. I have to admit that after reading the book I became very much interested in EJB 3 mainly because of its removal of legacy EJB2 boilerplate mechanisms and the introduction of "Spring" like features. The book is very cleverly written and easy to read. The authors make every effort to make the readers completely engaged on the topic. Although I don't use EJB3 for my day to day work, this book clearly gave me new perspectives on how Java EE is driven going forward.



5. My company's library basically gives me access to all books I want, so I used to have a big stack of big EJB3 books on my desk. But during 2 months of daily work with EJB3 I often found this book helpful where others weren't and almost never found it the other way 'round. Only exception: Enterprise JavaBeans 3.0 (5th Edition) That book sometimes just has a broader coverage, delivering details that "EJB3 in Action" doesn't. But still, "EJB3 in Action" remains the best-understandable EJB3 book with (almost) the best coverage of topics. I have now returned all other books than the 2 mentioned here to the library, and I always look in this book first.
   
   While I agree with Rob on the language issue, what counts is the result, and that is usually the best with this book.

4 comments about Ajax: The Definitive Guide.

1. §
   There is a LOT of code in this 950 page book. I guess there is something here for everyone because there is code not directly related to Ajax but is directed to HTML structure or CSS presentational aspects or to frameworks that may include Ajax conveniences.
   
   In fact, the amount of code may interfere with the author's object of appealing to two very different types of people with this book: Web developers and project managers looking for a high-level view. Except for some intro chapters and the odd breather between 10-15 page code listings, I don't think any project managers *I* have worked with would extract much from the book.
   
   The book has 4 sections:
   Part 1 - Ajax Fundamentals: the basic technologies that could form the core of a typical Ajax application.
   
   Part 2 - Ajax Foundations: approaches to standards-compliant structure, separation of the presentational layer and client-side behaviors. Code code code!
   
   Part 3 - Ajax in Applications: describes the specific implementations of these technologies into Web applications. More code!
   
   Part 4 - Wrapping Up: tips on optimization.
   
   In addition, there are some reference appendices on XML and XSLT; on JavaScript frameworks; on Ajax implementation risks; and most interestingly, a catalog of freely available Web service APIs.
   
   One thing I did not like about the code listings was the use of Prototype style $() function syntax. This means when I see something like:
   var titleText = $('title').firstChild;
   I had to check whether .firstChild was a reference to a Prototype object or a reference to the standard DOM object. If the standard object, it would have been a whole lot clear just to have written document.getElementById().
   
   The book index is actually pretty good. With 950 pages stuffed with content, you will probably be thankful for that!
   §



2. 'Ajax: The Definitive Guide' certainly is definitive. With 950+ pages of content, this book doesn't know the word brevity. Spanning 23 chapters and 4 appendixes, this book covers everything you would want to know about AJAX. From its history to how it's grown to where things are today and in the future, this text is very complete. If you are new to AJAX and want to learn how to use it in an extensive way, this is a great resource. My only qualm with this book is that I feel it is just TOO big in size. A 'Learning AJAX' book at around 200-300 pages would be a great companion book to have on the side, then switching over to this bible-size book would be a good transition. Overall this is written well, laid out in detail, and typical O'Reilly quality.
   
   ***** RECOMMENDED



3. My previous favorite, and most recommended, book on AJAX was the one by Crane et. al. because of it's completeness in covering the subject by taking a big picture view of Web 2.0 rather than just one technology. For developers though, the book by Holdener is probably the one to own.
   
   This book has some excellent information that seems to escape other books on this subject or is found across multiple titles. So even though it is certainly a large volume, I think there is some definite value in having quite a bit of related material in one title. For example, there are insights into JavaScript and use of JSON in programming the DOM (to name a few) that in my opinion made sense to include.
   
   If you are going to do rich, browser-based application work, you definitely want to consider this book.



4. While "Ajax: The Definitive Guide" is certainly exhaustive, it's hard to have confidence in a text so riddled with errors. Other O'Reilly titles I've purchased in the last few years suffer from the same problem: very poor copy editing. In a "Definitive Guide," this is inexcusable.
   
   Furthermore, he author's decision to rely on the Prototype framework is misguided. It saves a few lines of code per page, but one expects a "Definitive Guide" to define, explore, and use the actual objects and methods defined by the language itself, not those defined in one of many, many external libraries.
   
   It is also somewhat comical to read on page 10 that developers, rather than browser vendors, "are to blame for not adopting standards" and that they are "stuck with the mentality of the 1990s, when browser quirks mode, coding hacks, and other tricks were the only things that allowed code to work in all environments," and then to read on page 191 that "Yes, there are always caveats in the world of standards compliance" and that "Example 7-2 will not work in Internet Explorer because Internet Explorer does not support the CSS2 rules that are used to make this work." And on page 187 that "Internet Explorer does not natively support :hover on elements other than . For this reason, instead of using the CSS that will work for all other browsers, we must use this...."
   
   (It's hard not to laugh, too, at a sentence that begins with "To take the file menu example fully to the Web 2.0 level....")
   
   By the time all the errata are corrected and a second edition issued, it might be appropriate for the author to wag his finger at developers who can't yet afford to to be totally standards-pure, but by then the faddish jargon will seem very dated.
   
   And until O'Reilly starts employing copy editors, I'm not buying the first edition of any title they release.

5 comments about More About Software Requirements: Thorny Issues and Practical Advice.

1. Karl Wiegers is the person I recommend all my employees to read. This book is even better than 'Software Requirements, 2nd Edition' by Karl. He gives practical advises together with theory and important references. This book could be used as a tutorial for requirements engineers. One of the best books in this subject area.



2. This book addresses specific topics related with software requirements and the section "10 cosmic truths about software requirements" alone is well worth the read. The definitive book on software requirements remains the "Software Requirements" by the same author.



3. This is an excellent book which discusses the practical aspects of requirements engineering. Is a good companion to the original Weigers book.



4. I found it easy to read and very quickly full of my own highlighted pages and sticky notes for reference. This book will be in my must reread shelf at my desk. Since gathering requirements is a huge part of any quality product this book will help you get your hands around the task.



5. This book is easier to read than the book that it is the sequel to and has specific topics. They may or may not add value to your life, but does add value to the original book to get a little more insight into how real life works on software projects.

3 comments about The Essential Guide to Flex 3 (Essential Guide).

1. I have learned a great deal from this book. Along with taking a course with the author and reading this book I have learned how to do things the correct way and have reaped the rewards from it. I would recommend this book to anyone looking to learn Flex quickly and/or catch up on whats new in Flex 3.



2. Good Book. Would have raised rating to 4 1/2 stars if that was an option.
   Enjoyed reading and doing the exercises. Not many errors, few but they where small. Wish Chapter 15 (AIR) would have been a little longer with more detail.
   
   All in all, a good start. Introduced to many topics, ColdFusion was a good one.
   
   Thanks



3. If you don't know Flex 3 and want to learn the basics and then some, well then this book might just be for you. The author takes you through Installing Eclipse and Flex Builder 3 (FB3) which I found very informing. He then takes you through some of the different areas in FB3. The chapter on ActionScript (Chapter 3) is not a very good one. You will need a different book for ActionScript reference. You then go through some of the "essentials" of Flex 3 to understand how to build an application.
   
   I was a bit confused at times but it might have been because of the speed I was going through this book. If I would have slowed down a bit, I think it would have been a lot clearer. Also, I am new to Flex so it was learning from scratch for me.
   
   This book does not come with the files, nor can you download them. I really think if it had the files it would have been a MUCH better read/work along. There are a few errors in the code and you have to guess at times as to what it should be. I could not get one section to work at all (as was shown in the book).
   
   If you want to learn Flex 3 or get a better understanding of Flex 3, then I would tell you to read this book. The information you will learn far outweighs the few errors and lack of files. I've always said the best way to learn code, is to sit down and type it out. You will be doing a lot of this. Good job Charles!

4 comments about Ethics and Technology: Ethical Issues in an Age of Information and Communication Technology.

1. This book was on the prescribed text list for the masters I am doing (Master of Informaiton Technology) and I must say I was pleasantly surprised to read it. Being a technical (engineer) person, it's a generalized opinion that this group (enclave?) we like mathematics, science and engineering books, but not so called 'arty farty' stuff like philosophy. Speaking for me personally, isn't far from the truth...So I thought...groan, not another one of these idealistic, pointless, ultimately altruistic and futile failures to read. Indeed not! I actually enjoyed reading it! (shock-horror). Tavani uses the ploy of relating his ideas to real-life situations (stalking, cracking, etc). This lends the book a serious air of legitimacy. The ivory tower is nowehere in sight. He doesn't lecture at you like you're a poor, misguided computer geek who could never possibly understand human morals and ethics in a digital world (the point is to help you do that...which Tavani does).
   
   Back to the point: the book builds form the point of view that you have never been exposed to ethics. You get a grounding in ethical theories and then move on to learning how to evaluate ethical issues (kind like logic in mathematics without the symbols). He talks about codes of practice and your moral responsibility as a somebody who works, creates or manages a little corner of cyberspace. It is at this point that the book leaps forward into relevant (if somewhat shallow treatment) of the major issues ike privacy, piracy, crime, security,freedom of speech and equity. These are also posited through scenarios and then the ethics involved are developed through direct discussion of these scenarios. And as I alluded to previously, these give the book an excellent 'hook'. They make the theory real and relevant and rather interesting (and sometimes tragic: you'll see what I mean when you read the first scenario involving a teenage girl stalked thorugh the net and ultimately murdered in realty).
   
   This is a provocative book, but in a subdued, subtle way. The author doesn't speed feed you heaped spoonsfuls of moral outrage with lashings of indignant pontification, just ideas (and these are ever so valuable) in a considered manner. I think the author has really succeeded here. If he can make a totally 'technical' person like me actually enthusiastic about reading it, then that's truly indicative of the book's quality.
   
   The price may be a little high for what is a pretty thin book in a physical sense. Ideaswise it is quite rich, so that's the price you pay (it this ethical? ideas are only available to those who can affort it!) That aside, I got a lot from this little book and so consider it money well spent.
   
   All in all a good 'starting' book for cyberethics! Thumbs up! However consider you may find yourself supplementing it with other braoder, deeper works as you progress because it is a rich field to learn in. Tavani will open this vista up for you if you approch this book with a willingness to put aside your prejudices and listen to what he has to say.



2. It seems that every time you turn around, there's some news story in the industry press about the ethics or legality of some aspect of technology. To help myself understand some of the underlying issues a bit better, I decided to read and review Ethics & Technology: Ethical Issues in an Age of Information and Communication Technology (2nd Edition) by Herman T. Tavani. While not the easiest or most riveting read, I did come away with a better appreciation for the field of ethics.
   
   Contents: Introduction To Cyberethics - Concepts, Perspectives, and Methodological Frameworks; Ethical Concepts and Ethical Theories - Establishing and Justifying a Moral System; Critical Thinking Skills and Logical Arguments - Tools for Evaluating Cyberethics Issues; Professional Ethics, Codes of Conducts, and Moral Responsibility; Privacy and Cyberspace; Security in Cyberspace; Cybercrime and Cyberrelated Crimes; Intellectual Property Disputes in Cyberspace; Regulating Commerce and Speech in Cyberspace; Social Inclusion, The Digital Divide, and the Transformation of Work - The Impact for Class, Race, and Gender; Community and Identity in Cyberspace - Ethical Aspects of Virtual-Reality and Artificial-Intelligence Technologies; Pervasive Computing and Converging Technologies - Ethical Aspects of Ambient Intelligence, Bioinformatics, and Nanocomputing; Glossary; Index
   
   Having never taken a class on ethics or critical thinking, I found the first three chapters interesting. Tavani builds the foundation of how to define and describe cyberethics, as well as how to determine and argue the case of what is "moral". These chapters are a concise course on how to build an argument and support it properly. After those three chapters are done, the concepts that were built are used to examine many different facets of computers and life, and how ethics come into play and shape how we think. There are the subjects you'd expect, like digital rights and security. But he also covers issues that I don't normally think of when dwelling on computers and ethics... gender, socioeconomic classes, race. First you have to determine if indeed those things are ethical issues, and if so, what responsibility do you have in those areas.
   
   On one hand, the book is thorough and detailed. It's meant to be a textbook on the subject, and as such it delivers. These are the types of academic discussions and debates that you'd expect in a formal setting. I was somewhat disappointed, however, when it came to conclusions. Both sides of each issue were debated (even when I didn't even think there *was* another side), but resolution was elusive. I suppose I'm supposed to take this information and draw my own conclusions, but instead I came away with "so everything's right *and* wrong". Since I tend to want to get down to practical issues rather than deal with abstracts, I found it hard to come to any resolution at the end of each chapter.
   
   Definitely good material, and worth reading. But it will make you work and think.



3. While this book would not normally be one that I would purchase to read on its own, it was the textbook for a course on computer ethics that I took and I was pleasantly surprised to find the textbook written in a very approachable matter.
   
   The text starts off with an overview in general ethical theory before starting in to the focus of the text - various issues and how they apply to the growing use of computer technology in the modern world. Some of the topics covered include surveillance, privacy, and file sharing among others. Included with the various issues are up to date examples for recent cases and point/counterpoint perspectives on the topics.
   
   The text does lose some points due to the fact that the last few chapters run a bit thin and could stand to be expanded a bit, but as a whole the text is quite detailed and provides plenty of citations to allow the reader to find attentional information.



4. The book was received very quickly, and it was in excellent condition. This is a great way to save on textbooks for school!

No comments about Introduction to Language Development.

2 comments about An Introduction to Programming Using Alice.

1. For non-programmers who want to learn an object oriented language, Alice is a nice choice. At least as a pedagogic vehicle. As far as I know, there are no actual [or few] actual jobs for Alice programmers. But at the primary or secondary school level, Alice gets the main concepts common to many commercial OO languages across to students.
   
   Herbert introduces these concepts at a deliberately slow pace. Suitable for most of the targeted audience. The screen captures of the user interface are quite pretty, and help to hold the reader's attention. As compared with learning C++, say, where there is no intrinsic GUI. Plus, the mapping of conceptual objects to graphical objects in Alice is its main attraction. Very intuitive.



2. Not only did I save money from buying from Amazon, it also arrived in time for my first class. Excellenct service.

5 comments about Programming in Lua, Second Edition.

1. Buying this book does more than support the Lua project. Having the book available will change your opinion of integrating script with C code! "Progamming in Lua" is a well-written text that makes using Lua practical. All of the best features of Lua are covered; the sample code is concise, clear and complete.
   
   Lua is very different from C, and so allows a programmer to easily do things that are difficult in C. That makes it a perfect companion language. The only obstacle is training a C programmer to use it! That's where the book becomes useful. It's a quick read and covers all the essentials.
   
   Even better, Lua is so well-connected to C that it is easy to switch back and forth in the course of a typical programming day, writing performance code in C and high-level logic in Lua. It is even possible to easily interact with Lua data structures in C without writing Lua code for situations where the data structures are desirable but Lua code isn't required. If you're looking for a scripting language for your next project, you need to know about Lua, and this book is the quickest way to make an informed decision.



2. Naming this language after the moon is ironically apropos, as many of its lunatic creator's cognitive processes seem to randomly scramble themselves according to the phase of said moon. I'm no language designer myself, but if I were trying to come up with a high-level scripting language that would appeal directly to C programmers, the last thing I'd want to do is start array indices at 1 rather than 0. Sure, you have the option of altering this behavior in the constructor, but in the author's own words:
   
   "I do not recommend the use of arrays starting at 0 in Lua. Most built-in functions assume that arrays start at index 1, and therefore they will not handle such arrays correctly."
   
   Talk about giving you just enough rope to hang yourself. But it gets even better. Array elements in Lua are to be removed by assigning their indices the value of nil. This is all well and good, but, again in the author's own words:
   
   "Lua uses [the nil] value as a sentinel to find the end of the array. When the array has holes--nil elements inside it--the length operator may assume any of these nil elements as the end marker. Of course, this unpredictability is hardly what you want."
   
   No shoot, Sherlock. So why not get rid of that unpredictability? As I read further I came to the conclusion that this decision was made because doing otherwise would spoil the running theme of the language. Another favorite passage comes from page 32 when discussing the numeric for loop:
   
   "you should never change the value of the control variable: the effect of such changes is unpredictable."
   
   Great! I love unpredictable results. They make so much more sense than raising a predictable exception or pointing out a predictable old syntax error. Let's see now... How else can we anger C programmers? How about if we make it so "a break or return statement can appear only as the last statement of a block"? Wonderful! Now let's get rid of one of the primary attractions of high-level scripting languages--regular expressions--and say we can't include them due to size concerns (we really need to be able to brag about our entire distribution fitting on a single floppy disk, and the PCRE library is just HUGE).
   
   These things are marginally less obnoxious than Python's significant whitespace, but still obnoxious, and apart from the multiple return values thing, I really didn't find any compelling reason to join the Lua fanboy camp in this volume. Maybe if I were a Warcraft player I'd feel differently.
   
   As for the book itself, the writing is terse and very obviously coming from a non-native speaker. The typesetting is atrocious (good typography is one of those things you never really appreciate until it's gone) and the entire thing looks like it was printed on an old laser printer that was low on toner at Kinko's. If it were cheaper, I wouldn't care, but it's not, so I do.
   
   Stick to the free PDF if you really have to learn Lua for something. The changes in 5.1 are not significant enough to warrant a second edition, and the flimsy, smudged paper is really not worth paying for.



3. Good examples, suggestions, and notes. Is a must have for any one looking to program in Lua.



4. One of the best programing language books I have read. If only the programing guides for other languages could be this clear and concise.



5. The information in the book is clear, easy to understand, and worth reading. The formatting of the text, the fonts used, and the overall style of the book is lacking. The end of the book was actually a few mm shorter than the spine on my copy, but nothing was cut off, so it doesn't matter beyond looking a little odd.
   
   I would buy it again, even if the previous version is available for free online. It's great to read when you're not near a computer, as (for a programmer) the book is easy enough to follow without needing to try every example yourself.

5 comments about Lessons Learned in Software Testing.

1. Lessons Learned in Software Testing
   
   As a new QA tester I have found that books written by Cem Kaner and associates are extremely helpful. This book in particular (Lessons Learned...) has been a wonderful help to me. I was able to be on guard before I had to learn the lessons the hard way. This book is easy to read and to the point. It is written in a way that the layman can easily uderstand it. This book is extremely insightful and is a good buy for anyone new to the field or not.



2. Through a series of nearly 300 "lessons", the authors share their accumulated wisdom about how to test application systems - not so much which buttons to press but more how to establish and manage a test team, plan the work and dynamically adjust the testing process according to what is found and how much time is left.
   
   The chapter titles ably illustrate the book's scope: 1. Role of the tester; 2. Thinking like a tester; 3. Testing techniques; 4. Bug advocacy; 5. Automating testing; 6. Documenting testing; 7. Interacting with programmers; 8. Managing the testing project; 9. Managing the testing group; 10. Your career in software testing; 11. Planning the testing strategy; [Appendix] The context driven approach to software testing.
   
   I would definitely encourage anyone who thinks `test automation' is a great idea and is perhaps contemplating the purchase and use of automation tools, to read chapter 5 before they commit the budget and finalize the project plans. The authors eloquently explain the advantages and disadvantages of common automation techniques such as user input replay tools, providing a real-world counter to the tool vendors' optimistic sales pitches. They don't say "Forget it", rather "If you can live with these significant drawbacks, automated testing may be useful for a certain subset of testing activities". This is a good example of the pragmatism and wisdom found throughout the book.
   
   The book is not an academic treatise full of theoretical constructs/models and testing methodologies. Nor is it a step-by-step manual on how to test a system. It is an excellent read for testing practitioners who are seeking or at least open to advice on how to do their jobs more effectively and efficiently. "This book is for anyone who test software, anyone who manages testers, and anyone who has to deal with testers in their software development projects. That includes project managers and executives." The hints and tips plus career development advice are valuable for testers, especially if they have a few years testing under their belts already. The technical content is minimal and should be readily understood by any IT professional while the management advice should be appreciated by those with management experience or who aspire to become managers.
   
   The book strongly encourages testers to work with developers and project managers, becoming an integral and valuable part of the team rather than an impediment to progress and a threat to delivery deadlines (lesson 12 is typically direct: "Never be the gatekeeper"!). The subtitle's reference to being `context driven' introduces a dynamic approach to testing, relating test activities to the development lifecycle and promoting those that will be of most help to the project at any point. The approach is described further in the appendix but is only subtly referenced elsewhere, unlike certain other books that insist on pushing their One Big Idea down the reader's throat at every possible opportunity.
   
   All three authors clearly have solid testing experience, some 60 work-years between them. There are also numerous (but not intrusive) citations to other helpful resources, further demonstrating the authors' pedigree. Cem Kaner, a consultant and IT professor at Florida Institute of Technology, was the lead author of Testing Computer Software, 2nd Edition, one of my all time favorite IT books. Cem also practices law. James Bach is the founder of a software testing and QA company with silicon valley experience. Bret Pettichord is an independent consultant who edits the Software Testing Hotlist and founded the Austin Workshop on Test Automation.
   
   The "lessons" format leads to a somewhat disjointed flow in places although overall the book is well-structured. At times, successive lessons are directly contradictory, again emphasizing the need for readers to be both alert and open-minded. This is another example of being `context-driven'. Which lesson you choose to follow depends on the circumstances facing you, a form of contingency planning if you will.
   Unusually for a published book, several critical comments from reviewers of the draft, as well as occasional differences of opinion or approach between the three authors, are included as footnotes or asides. The authors openly acknowledge the ambiguities and leave the reader to think about them and make the final decision - I like that. This is a book for grown-ups. There are valiant attempts to describe and promote `the tester's nose', that seemingly innate ability of experienced and successful testers to sniff-out aspects of the system that are likely to harbor serious bugs and to design targeted tests that will reveal them. The advice on unstructured `guerilla testing' is not quite so useful, in my opinion, but I'm impressed that the book even tackles such ephemeral concepts.
   
   Even if you only learn something new from a few of the lessons, this book is well worth the purchase price. Testers relatively new to the profession will learn more than grey-beards but even they will probably find some of the suggestions make them re-think long-established ways of working (habits) and subconscious assumptions (prejudices). In the main, the lessons are pragmatic. Some are a bit contentious, perhaps deliberately, and most are both thought provoking and helpful.
   
   Bottom line: recommended for any thinking person involved in application testing including development project managers and IT auditors.



3. This is a good text on how to avoid time consuming mistakes in software testing. Experience is the best teacher around and this encapsulates that. This would be a good book for the novice to learn from. It may save you from going down a "rat hole" in your testing thus wasting time and resources.



4. *This book is a must for those organizations that has trouble figuring out how to slash down their budget without sacrificing their effectiveness in shipping quality software.
   *This book will open your mind that spending much time in creating test steps is Good but not excellent.
   *This book is unique. The author will not force you to follow what is written inside but instead give you idea to invent your own model cognitively.
   *This book will never be obsolete because the lessons stated inside is generic. I always bring this book wherever I go until I memorized it all.
   *I have so much to say but to make it short this book passed my criteria in my own idioms.



5. I can't say enough good things about this book. Maybe it's because the authors think the same way I do. Academic books on test process have never appealed to me. But this book cuts through the contrived processes and flow models and spells it out for you: these things work, these things don't.