Software Books

The problem I've seen with technical books is that either they are in tutorial/textbook format which includes lessons and then review questions at the end of each chapter, or they are purely reference type books ideal for looking up things on occasion and not really good for a beginner to learn the subject matter. This book was the first one I felt that was ideal in both textbook form as well as a reference book for looking things up.

The chapters were basic enough for the beginner to grasp the material, and the lessons were rife with hands-on examples which I thought was the best part. I like to try things out as I go through the lessons and so the material was very useful for me.

The printing of the material was interesting and draws the reader into the subject, important notes and pitfalls are highlighted between the text to avoid the paragraphs from becoming too long and drawn out. The writer's diction is sometimes humorous to avoid the reader from losing interest.

The book is kind of bulky and thick so as a consequence of regular use, the glue based binding gave way somewhere in the middle of the book so when I open it, the first half of the book is attched merely by a shred to the second half, so I have to be careful now when I lookup things in it. I wouldn't trade this book for anything.

I have never taken any instructional classes on Perl scripting and can safely say that everything I know about Perl scripting I've learned from this book. That being said I am able to write fairly sophisticated perl scripts and have the ability to understand fairly obfuscated perl code without difficulty. I use perl as a very strong and useful tool in my day to day tasks for scripting and text processing needs and I often dazzle and amaze my colleagues at work with the tricks I'm able to pull off by using perl scripting and I owe it all to this book.

In short, I give two enthusiastic thumbs up for this book and the 5 star rating that I gave this book was merely due to the amazon limitation on the number of stars you can give in your review.

I started learning Perl two years ago. I first browsed libraries, free tutorials, news groups etc... It was nice for the beginning but soon enough I understood that's not the way :)

I started looking around for good Perl books and somehow got to this one. I think I can clearly say, that this book did the work. Teached me Perl from the ground up. I'm now planning on buying "MySQL and mSQL" to start working with databases. I also consider buying "Mastering Algorithms With Perl" & "Programming Web Graphics with Perl & GNU Software".

Anyway, if you want to start learning Perl, buy this book. I also use it as a reference.

The book is a good and detailed tutorial for all novices who want to learn Perl. No hit around the bush stuff and the chapters were well thought of. Credit should be given to the author and the publishing group for these helpful information. The Source codes on the CD-Rom comes handy when when you want to test out the sample codes in the book. The questions at the end of each chapter is a good revision after scanning the chapter. I strongly recommend those who want to learn Perl to get a copy of this book as their first book.

After the Camel book, of course. This book is very well paced with well thought out examples. I needed it as a refresher last year, and now use it as a reference.

The only down side is that the Web Based interactive segment is no longer available. not a big deal since it's the same quizes as in the book, but there was a gee-whiz, isn't it fun factor to have it available online.

This book covers everything from soup to nuts. It starts the learner off slowly with the basic perl syntax and then smoothly moves into subroutines, OOP, DBI modules, Security, etc. all with the same interesting and amusing style.

I don't know if it's mentioned in the Editorial review, but the author is the Editor of The Perl Journal (www.tpj.com) which is a magazine devoted to the perl programming language. So Jon Orwant *knows* his topic.

I've read and use most of the Perl books out on the market today, but none comes close to getting you going well with Perl as does Jon Orwant's book. I still use it as a reference today, but it is the best any money can buy for learning Perl. I'm back buying another copy because I loaned mine to a friend and I miss it so much that I want to make sure I'll always have a copy handy. My old copy is so well worn that a fresh copy is enticing also. As for extras in the book: the quizzes are great for testing your understanding, and someone has done a great job at proofreading this book -- I don't know whether that person is at the Waite Group or is Jon himself, but I know that anytime I have questioned an answer, or a script, or anything in the book I have always found the book to be accurate on closer inspection. It is very much like the Camel Book in being authoritative -- what Jon says is Perl Gospel Truth - if I had to pick two Perl books, I'd pick this one for learning and the Camel Book for ultimate reference. Jon's book should be rated a 5 and a half star - this is the best that it ever gets!

No obtiene la quinta estrella por no hacer referencia alguna al manejo de los archivos BVH. Por lo demás, genial!

This book has become one of my references for Poser 6. It's clearly written and covers topics from basic to advanced. I recommend this book for anyone learning or using Poser 6!

It was very easy to follow and made it easy to learn Poser 6.

I avoid buying software books because many of my past purchases were a complete waste of money. The authors rehash the software's free manuals and provide explanations and tutorials so basic that it seems their target reader is somebody who bought their first PC just last week.

Based on strong reviews, I took a chance and bought Practical Poser 6. I'm not going to cover the content, which is already described very thoroughly in other reviews here. I'll just say that if you have tried to use Poser without any tutorial or learning aids, this book is for you. I had a copy of Poser 5 and had just bought Poser 6 a few weeks before getting this book. My measure of a good instructional book is how much it taught me that I didn't know already. I estimate 50-60% of this book contains info that I'd only have learned by painful trial-and-error, and was really useful to me. And this is not to say that it's for experienced users only -- whether you're just starting out with Poser or already have a few years of experience, there's some explanations, tips and general good reading in this book for you. Highly recommended!

I found Practical Poser 6 a valuable training tutorial into the world of 3D graphics. Not only did it explain the functions and usages of Poser 6 in understandable terms, it illustrated examples in easy to follow, step-by-step instructions. This book is a recommended must-have for individuals who are thinking about entering the realm of 3D graphics or serious artists who want to refine their technique and squeeze a little more 'mileage' from their programs. A first-rate, well written book in it's field.

This is among my favorite computer science books. I read the first edition straight through from cover to cover, even though I had some prior knowledge of the subject. I have since purchased the second edition, which exceeds the high standards set by the first edition. Scott's book would have made the programming languages course I took as an undergraduate much more enlightening, had it existed at the time.

As a software engineer, I tend to be picky about my books, but this one is very in depth and a good read. You will learn a lot about different programming languages, and why certain languages are better than others for solving different types of prroblems.

Over the years the Compilers: Principles, Techniques, and Tools (2nd Edition) (also knwon as the dragon book) has become the de facto standard for introducing compilers and related topics at universities. This is very unfortunate because "Programming Language Pragmatics" is in a completely different league and should be the one used instead. It gives the student (or the self taught) a complete and through overview of parsing, grammar, automata theory and other key language constructs. What really differentiates this book from others (and most notably the (in)famous "Dragon Book") is that it does so in a easy to understand manner and with lots of well written examples.

Many people find compiler and language theory to be dark magic, and it would be wrong not to acknowledge that these subjects are considerably harder than say creating a web page in PHP or writing a small Java/C# program. But much of the confusion also stems from the long history of porly written books which all have lacked explaining key areas or assumed that the readers just know some obscure CS topics beforehand. This book does not travel down that road, it is well written, contains both simple and advanced examples and is simply a delightful read.

Overall, "Programming Language Pragmatics" (PLP) is a very good book. According to the Preface:

"It aims, quite simply, to be the most comprehensive and accurate languages text available, in a style that is engaging and accessible to the typical undergraduate....

At its core, PLP is a book about how programming languages work. Rather than enumerate the details of many different languages, it focuses on concepts that underlie all the languages the student is likely to encounter, illustrating those concepts with a variety of concrete examples, and exploring the tradeoffs that explain why different languages were designed in different ways."

I'm not knowledgeable enough to pass judgment on "the most comprehensive and accurate" part. But, I'm pretty happy about the book meeting the rest of those goals. I read through the book on my own and have only a few significant gripes:

- Chapters 2 (Programming Language Syntax) and 4 (Semantic Analysis) are tough to get through. They're basically trying to teach enough about Alphabets, Languages, Regular Expressions, Context-Free Grammars, Finite Automata and Push-Down Automata for the reader to understand what the rest of the book is based on. I've read Cohen's Introduction to Computer Theory, which is dedicated solely to this material and I still had some trouble. With an instructor in a class to walk through the things, it should be doable. But, for a person reading the book on his own, ugh.

- All of Section III: Alternative Programming Models, seems to depart from the format of the rest of the book (as noted in the Preface) where the author talks about the concepts and then how the different languages implement them. Instead, he focuses on the languages themselves and almost seems to be trying to cram a primer into his text. Since the section seems to be a special case, it wouldn't be so bad except that the languages covered are a bit out of the mainstream and so that degree of depth gets pretty unreadable at times. Again, with a professor around, things would be better.

- At a more pedagogical level, the author has a tendency to merely explain what his example Figures are doing in general terms. The problem is that a lot of the code/pseudocode involves fairly advanced structures in several languages (many of which most people won't have run across). It would have made things a lot easier if he had walked his way through each of those Figures line-by-line and explained what each line did. Once again, this wouldn't be that much of a problem in a normal teaching environment since a professor could do it.

Other than those three things, this is a very good and readable book. I rate it at four stars out of five.

Every good programmer should know more than one programming language, that much is almost a consensus. But more than that, every programmer should educate himself about programming languages in general, what they mean and how they work. It's important to know at least the major programming paradigms, because they form the "mental model" of computation that is available to a programmer in a language from that paradigm.

And then it's always illustrative to know about the differences in many common languages, to see where different decisions have been made and what are the consequences. To know that certain legacy languages (e.g. C, Fortran) have features that were not designed because they were the "best" option (for some definition of best), but because the design was constrained by what technology was currently available.

This knowledge is not only required of compiler writers. It should be required of every good programmer. Compiler writers, of course, must know this, and probably in more detail. But Scott's book is a good resource about programming languages, in a level of detail that I believe adequate for all programmers.

There are two main kinds of books on programming languages: they are "survey" and "implementation".

Survey books show how things work in a lot of languages, comparing them along the way. Often the comparison gets down to small details that can affect the meaning, or semantics, of similar programs written in these languages. These books contain one individual chapter for every major topic, and inside such a chapter all languages are compared in relation to the topic. For example, one such chapter covers "subroutines" and then compare a host of different languages on how they implement subroutines.

Implementation books are different: they show how to implement many language features, usually by presenting code for interpreters and compilers. The reader doesn't learn that Ada permits nested subroutines, but instead how nested subroutines really work and how to implement them in a language, for example. A very good book of this kind is "Essentials of Programming Languages" by Friedman, Wand & Haynes.

I normally prefer the implementation books. I'm not really interested if Standard Pascal permits functions to be passed as parameters or not; if I do need to write a Standard Pascal compiler I'll look for a reference manual. I much prefer to know how to implement functions as parameters, and be done with it. Comparing minutiae about extant programming languages can sometimes be very enlightening, and sometimes be mostly dull.

Scott's book, however, really shines because it mixes feature descriptions and implementation details in the presentation. It does the usual routine of comparing a lot of different languages, most of the time the more popular ones like C++ and Java, but it then shows how the implementations differ because of differences in features. The book strikes a good balance between "language design" and "implementation" approaches, although it is clearly slanted towards design, and so more of a traditional "survey" book.

It wins over other survey books by including implementation information about almost every topic, and by the clear writing and style. Also, most survey books concentrate on mainstream imperative languages (nowadays C++, Java, C#) and leave other paradigms to chapters at the end. Scott's book is a bit better in this respect: the presentation often includes Common Lisp, Scheme and Standard ML in the comparisons. There are separate chapters about functional and logic programming too, but considerations about functional programming are spread in the whole book. This is important because paradigms change, and a good programmer must be able to adapt.

It's a good reference for language implementors and good education for most programmers. I look forward to the next editions.

While this book covers all the significant technology in the area, it is a much better read for all those things you wondered about in Sci Fi Could they really do that? Also the policy issues are critical to our privacy rights and conversly national security.

Anyone who uses a mobile phone, relies upon oversees Internet connectivity, or worries about personal security should get acquainted with this book. Mr. Vacca has once again produced a very accessible yet easily readable tome on the dangers and promise of satellite encryption. Pick it up and you'll learn about or government policies regarding satellite communications management and security. By the time you put it down, you'll understand everything from pagers to the electronic battlefield. It's a must-read!

Great book - detailed and technical, but still a good read

As always, John Vacca provides an incredible level of detail in a readable manner. The Internet implications are particularly applicable to almost any reader. In our case, where the line-of-sight constraints of radio transmission in our wireless WANs are forcing us to look at satellite options, this book is an invaluable resource. And the tales told herein about encryption break-ins and techniques make fascinating reading in their own right.

Technical from orbit to chip, and immensely readable as well!

I think that the tittle of this book is a bit misleading. If one reads through all the enthusiastic reviews of the book one can actually get a clear picture of what it is about. It is a general overview of politics of encryption with some technical information included in between. I cannot understand the reason for more than one hundred pages of information about different types of military equipment. Yes, this book is interesting but it is not about cryptography and encryption. These subjects are only a small part of the book. I returned Satellite Encryption after very thorough consideration.

A "must read" for anyone in manufacturing. It is the basis for all modern manufacturing, and for any business process or flow. The author describes the two pillars of the Toyota production system as autonomation and just-in-time. He explaines the six rules associated with the kanban. He also describes the seven wastes and the value of asking "Why" five times. The book is very easy and quick reading, and provides a complete backgroung to the Toyota development and success.

Toyota Production System: Beyond Large-Scale Production
Great tool for understanding basics and roots of TPS

I got this as a present for my father for his birthday last weekend. He has already started reading it and making notes. It is everything we hoped it would be and met his expectations. I would recommend it for marketing students, teachers, and anyone interested in that type of thing.

"Toyota Production System" was published in 1979 in Japanese and, in English in 1988. It is the source material on the toyota production system and, in my view, it is often good to go back to the source. Sadly, I found this book disappointing. The writing style is clunky (perhaps a poor translation) and the book lacks structure; being more of a semi-random collection of points than a development of ideas. Nevertheless there is some interesting stuff in here. The honesty that this is a long slow process (taking Toyota 30+ years) is refreshing, and I hadn't realised that Mr Ohno ranked kanban (with quick changeovers) as the core of the system and essential to success. Often in lean kanban seems to be a bit of a side issue: here it is vital. Also there is an interesting analysis of some of Henry Ford's early writings compared to TPS. This would be good material for a student essay. However, for the philosophy of TPS you will get much more out of "The Toyota Way" or "The Toyota Way Fieldbook"; and for the tools of lean go to "Lean Production Simplified" or the many other books in this area. Overall this book is a bit of a let-down I am sad to say.

There are many myths around the Toyota Production System (TPS). Ohno Taiichi merits my deepest respects, considering he was able almost a half century ago to observe and learn from others. Considering the simple target given to him, to "catch up with America" he studied in-depth the work of Ford and recognised the idea of copying the US supermarket system for his operational purpose.

The book describes very well what constraints he was given from the owners when Toyota started to get into the automotive business and what path they followed until the first fully operated TPS plant went operational at the 60s.

Many thinkings of Ohno Taiichi are still actual. He is capable of bringing key problems to the point: efficiency gains are worthless until they really lead to cost reduction. Unfortunatelly we all now the opposite from this wisdom - and many "growth-strategies" of companies today are nothing else than to try to increase business with the same workforce. Furthermore the author gives good examples how Toyota handled different issues, as e.g. the syncronization of production with final assembly.

The reader will not find any operational theory or formulas in this book and if you are looking for books teaching you about designing and sizing Pull-systems you should look for books as "Kanban made simple" or similar. TPS is not about installing software than about eliminating everything which is waste and does mainly not contribute to the succes of your business.

Anyway this book is a must read for any readers interested in first hand information about the basis that made TMC what they are today - a business model developed by smart people many years ago and dearing to ask simple questions, to find sound and robust solutions and to steadily develop the system and its people working in it.

My deepest respect to Ohno Taiichi,
Domo arrigato,

Oliver

Well, I can't say much that the other reviewers haven't already said. This is a terrific text that very clearly explains how things work in computers, right down to the finest level. Hyde writes in a casual, conversation-like tone (sometimes bordering on poor grammar) that makes this text a lot more stomachable than I would have thought. Typos are minimal (I recall maybe 4 or 5).

Now that I've been through the book (after maybe 2 weeks, at an easy pace), I can't say that I'm going to go write assembly programs. I can say that I know a great deal more about how computers work, and how I can write code that works more harmoniously with computers. My background is mechanical engineering with a ridiculous dose of electrical engineering, so a lot of the concepts presented were review for me (digital circuitry, binary math, etc)...but it is always good to hear the same material again in a different way. As I said before, the casual tone makes the material easy to follow, as well as Hyde's very clear explanations. However, as a mechanical engineer my programming background was just "writing code," i.e. how to get various programs to run correctly. I read the chapter in the text on memory twice- I found that chapter alone to make the book well worth the money to me, as I am currently writing codes that demand every inch of speed and memory that the computer can offer.

So overall, its a good book, worth the money, and worth taking the time to read.

This is a great way to understand data flow at the machine level.

I especially like the part on memory and IO.

Author has explained low-level concepts lucidly. It is easy on eyes. Basic concepts become very clear. It is one of those 'can't keep down without reading few chapters at a stretch' kind of technical book. Very few books have this edge. Just don't feel like stopping reading it.

Beginners must read this book before attempting to read more in-depth low-level technical books. This book is a must for people who are exposed to high-level languages but have not studied Computer Science.

This is a great book but I have to disagree with the overall viewpoint. I've been doing embedded programming for a while and if that's all I'd ever done I would totally agree that understanding low level concepts helps write better code. However, I also write a lot of code in C#. People who normally use high level languages such as C#, VB.Net, or JAVA are probably not going to benefit much from this book. These languages are so far abstracted from the hardware level that the concepts are hard to apply anywhere. On the other hand, if you still use malloc on a daily basis, you need to read the book :) Anyway, the book is easy to read and I never caught any errors. If you want to learn about computers at a low level, then this is a great book to start with!

If you're like most IT people out in the workforce today, you've got pressures from all sides - deadlines, keeping current with changes in platforms, hardware, software tools, etc. Gah! It never ends!

So, you pick up these "Write Great Code" books, thinking that you'll be a better programmer.

And it's interesting in a way that you remember when you were just getting into the IT field as a student and later as an employee and maybe now as a consultant or contractor.

But, then you realize that this is like thinking about how your car's components are working while you're driving madly to work on some beltway. Only your skills as a driver can keep you from getting hit by a big semi, not the working knowledge of your V8 engine. Guys who work on their cars on the weekend, know more about them than you do, but hey, it gets you to work and back.

And so, you sigh and put the book down and concentrate on your SQL, or your VB or whatever else keeps you employed.

Why?

Because your users and your manager don't care about what goes on at the machine level. They want the deliverables NOW. The efficiency of your code is of no importance to them, though it is to you.

However, with enough discipline and some thought to what you're doing, you CAN make this book work for you, and get an edge over someone else's sloppy code and maybe even save yourself some programming time.

Because this book is for the guys who are the computer counterparts of the greasy-looking guys on the street who could tell you what's wrong with your car, even if you can't.

I won't do a lengthy review... just read the other 5-star reviews and you'll get the drift. This book is so easy to understand you can learn without a PC in front of you (if you're a VB6 developer looking to understand .Net). The explanation of what ADO.NET is all about is worth purchase price alone. No chapter is super comprehensive, but it's a great text to get you rolling in VB.Net right quick. As an MCSD and MCDBA certified developer, I wouldn't write such a great review on just any book. Buy it.

There is so much that is lacking in this book. First, it is not user friendly. It is difficult to follow. Second, it simply does not cover enough information that one needs in order to truly be able to use .Net technology.

Cover to cover this book sails through the hype dispensing nuggets not to be forgotten!!! .Net and C#-aholics had breathed so much hot air, I was having trouble find a place to start. Once received I put everything else aside. I used to use arrays, types, RDS, and ADO to get the plumbing done but now its OOP, and serialization from now on!!! I got so many good pearls from this book its ridiculous.

I have been programming in VB since 1992 and decided to move to VB.NET when it was released but found the learning curve was immense - until I bought the book of VB.NET. This book is my Bible, it sits besides my computer all the time. Without delving into the VB language, it simplifies the transition to VB.NET for the experienced VB Programmer. It's not for VB learners nor does Matthew propose that it is. If you know VB this is the book to ease the quantam leap from VB to VB.NET - explained in logical steps with excellent examples. I have had to EMail Matthew with a few queries and the response is always prompt and helpful.

There are certainly other books you need in your arsenal - such as Francesco Balena's Microsoft Reference - but this one is a must.

This book has a very good intention and concept - to introduce VB6 developers to VB .Net. In general it is a very good book. Not very deep, but good enough to start working with VB .Net and bee reasonably productive. So, if not for sloppy writing, I would probably give that book all 5 stars.
What do I mean by sloppy? For once, author uses terms object and class interchangeably throughout the book. Sometimes it is contextually understandable what he means, but often it might be very confusing, especially for people relatively new to OO. Then there are errors and typos in code examples. Some of them are also very confusing. For example: on page 80 author introduces the new VB concept - delegates. For VB6 folks this is something fundamentally new and strange.
In code example author defines delegate type and calls it ProcessFunction. Then he defines variable of this type and calls it ProcessDelegate. After that on the same page he shows how to use delegates and assigns value to ProcessFunction and retrieves value from ProcessFunction.
From the context one should understand that in the last two cases the variable ProcessDelegate should be used instead, and that this is just a typo. Yet, given that VB .Net now supports shared properties and methods, when Class (Type) name can be used where one expects to see Object (Variable), this types of mistakes are very confusing and annoying.
I would not go here into more examples of books imperfections. There are some more. Not terribly many, but enough to frustrate.
Would I recommend this book? Yes, if you have patience and some other VB .Net book to resolve inevitable confusions.
This could become a great book in its next edition if author takes time to make it a bit more accurate and precise.

I thought this was a well written book on the fundamentals of demonstrating and or presenting software. I am a big believer in "Discovery" it makes for a much better and targeted demo. I also particularly like the metaphor he uses of "crossing the bridge" and how applying the principles in this book can help our prospects bridge the gap. He has some great nuggets for sales people who are involved in enterprise or consultative sales. Don't let the title fool you,(not just for SE's) I would recommend this book for all sales people who are interested in mastering their craft!

Excellent Book!!!



Since 1988, I have conducted many system software demonstrations!!

Demonstrating to Win touches all of my experiences from small client engagements to some one pulling out the plug of a mini AS/400!

By reading this book, I felt like you were a spider on the wall recording my many demo successes and failures.

Good Job.





Kevin M. Lee

Industry Director:

High Tech & Electronics

SSA Global

8913 Metheny Circle

Tampa Florida 33615



C 813-495-0332

O 813-249-0961


Kevin.Lee@ssaglobal.com

This is an excellent how-to book for improving your discovery and demo skills for enterprise software sales.

Chapter 4 (Demo Crime Files) and Chapter 5 (Discovery Process) more that justify the price of the book.

I sincerely wish that all presales engineers would read this book before presenting to customers.

I read Demo2Win and fell in love with the concept. After years of demonstrating software, I always felt like I could have done better if I had more tools. Robert's book gave me those tools. The tools I remember from the book were simple. Just be a little different than the other person or company. The Discovery Phase in the long run will save you and your customer time. You will find out if you can supply what the customer needs or leave it to someone else to fulfill their needs. Why waste time. The Demo Crimes made me cringe because I know I've committed a few of them over and over. Now I won't commit those crimes because it's been brought to my attention by Robert.
After I read the book I asked my boss to read it. He read it and ordered about 30 copies for all of our salesforce to read. Each and every person that read it then praised it. It was kind of like the lights went on in everybody's head.
I'd recommend this book to any salesperson. I've already read it more than three times. I take it on each flight I make and read at least a few pages each time.
Thanks, Robert.

Demonstrating To Win is an exhaustive book on the topic of demonstrating software by experienced hand Robert Riefstahl. The author delves into the subject at hand with precision and detail through chapters like Demonstrating Is Not An Art!, Important Demonstration Concepts, The Demo Crime Files! and Your Demonstration Setting. There can hardly be a better resource than Demonstrating To Win for professionals in the industry. The book covers the obvious, mundane and elementary to the detailed nuances and tricks of the trade and aims to articulate the author's main thrust that in order to win the day the presenter has to build a bridge that the prospect wants to cross in order to reach you (and your software product).
Each chapter is augmented by a brief summary which offers a synopsis of the topic covered and the author practices what he preaches by offering his experience in plain language. There certainly are a couple of instances where the reader will notice the book's age and its year 2000 publication date, most notably during the technical discussions, but Riefstahl's guide is comprehensive and advantageous all the way through and still relevant to those demonstrating software to potential customers.

This is a very user friendly book. The ony thing that would make it better is if it were geared for Captivate 2. After going through this book, I feel that I don't need any organized teaching sessions for the skills.

"Essentials of Macromedia (now Adobe) Captivate" is the
title of the book. The promise is maintained when you buy it,
read it and follow its step by step exercises.
If I'm right, "essentials" are the things that come first and
foremost. When you are new to a jungle, a subject or an
application you want to get the essentials as fast as you can.
If the application you want to learn is Captivate, then Kevin's
book is the buddy on your side, the one with more
experience, the one that helps you with clear instructions and
useful tips.
The exercises on the CD are well written and work. They take
you step by step through the major features of Captivate.
The language is simple. Even for those, like me, that have
English as a second language.
In a matter of days you are up and running, creating your own
multimedia instructional materials.
Then you'll probably need other books, because Kevin's
Essentials has brought you, fast and safe, to the point you
can take another leap forward, to reach Station "Advanced".
Last but not least, Kevin Siegel is a "real person" that stands
behind his product. Like other reviewers before me, I wrote
him an Email and he answered promptly.

I really think this is the best software tutorial I have ever used, and I have used quite a few in my trillion-year career as a technical writer. It has just the right level of detail. So many tutorial writers leave major concepts and steps out because they assume that you know what they know. And you don't, that's why you bought their stupid book. But this one guides you gently through all you need to know to get firmly established in using Captivate. It was a great help to me when I suddently found a Captivate project on my desk and didn't know exactly where to start. Essentials of Macromedia Captivate helped me start at the appropriate beginning point. It also provided lots of handy tips that I'm sure helped save me a ton of time that I would have spent if I had tried to figure out the software by myself. I would reiterate, as others have here, that you need to follow all the steps in the book to get the most out of it. But doing so is well worth your while.

This book is the cheapest class you may ever have, and it is a good class. As you may have noticed there are not many books written on Captivate. It's a shame because Adobe's Captivate really is great program.

I am a freelance web designer and Flash animator in the Seattle market. Last year I wanted to learn Captivate and realized there are no classes in the Puget Sound area and only 3 books on the market.

I purchased this one and it taught me the program just working on the exercises at night. The book has not typos, a nice flow and they cover most of the program. It is a productive book and you see results quickly. Since then I have added E-learning to my list of skills I offer thanks to this book and the Adobe's Captivate.

I do admit I also purchase the Visual Quick Start book. But when I need to reference something I go to Essentials first. I will look at the example in the exercise I did and it will click right away, "Oh that's how I did it".

We purchased Kevin's workbook for our team to help us through the learning curve for a new tool in our group. Wow! Kevin's book really delivered and we were creating near finished product movies and company branded templates in a fews days. Kevin has also been very responsive and incredibly helpful via e-mail inquiries.

If you're a moderately skilled programmer, a self-learner, and you want to get beyond just "getting started" deploying and using Sql Server 2000 Reporting Services, this is the book for you.

I especially found the chapters on customized set up extremely helpful. The installation wizard doesn't offer a whole lot of options, and most of teh time you don't know fully how you want to configure it until you've tried it out. You'll get some good starters on rconfiguring your installation here.

You'll get enough basics to be ready to dive in, and then some tricks well enough beyond that to give you well on your way to devleoping customized solutions.

For a total beginner (which I definately was) this is a FANTASTIC introduction to Reporting Services. Three months after starting my first job as a programmer straight out of University, and now I'm the main person in the firm with Reporting Services knowledge - and it's all thanks to this book.

The writing style is actually excellent for beginners, as I was terrified by the prospect of reading such a mammoth. But these guys make it fun and interesting to read (right down to the jokes and sidenotes) and really do touch on everything you need in a useful manner without boring you.

And excellent resource that now never leaves my desk. I can only hope these guys do a SQL Sever 2005 one. I cannot recommend this book enough for those starting on Reporting Services. It really is the book to read.

And if you are looking for a book on SQL Reportin 2005 - I would still recommend this book to give you the basics and introduction which is unbeatable thus far.

I really the beginning part on the setup and installation of the reporting services themselves. At my firm we needed to set up a seperate server for this purpose and the IT group was swamped with another project and this helped a great deal. I still am workign on development but the book has been very usefula and easy to understand.

This book has been written from a VB programmers point of view. If you want to just start creating reports or if you're not a VB programmer (ie DBA etc) you may find this hard work.As another reviewer mentioned, you may find the authors' jokes and writing style to be a hit and miss affair.

Nevertheless, there is some depth on Reporting Services not to be found elsewhere that is quite handy.

Now that all the friends and family have promoted the book...

In order to understand something new, we all must relate that which we're learning to that which we already know.
Pete and Bill have a difficult time transitioning from campy comedians to thoughtful educators. To this extent, their writing style lacks any useful analogies whatsoever which might bridge the gap between the known and the unknown.

The book is full of droll and distracting fantasy references which are completely irrelevant to the subject matter, and are prone to taking the unsuspecting reader off task.

The potential purchaser should also be forewarned that the authors tend towards another immature trait of attempting to impress the reader with their linguistic abilities. Yet, to be effective at teaching they should have remembered to never use a complicated word where a simple one will do.

Many examples are rambling and inconcise, where step-by-step quickly degrades into an ambiguous and vague path.

Not every developer can obtain DOMAIN Authority in order to issue SSL certificates and it's too bad that the authors don't allow for this type of scenario, especially when a reporting system is on a VPN.

All of the content is there, but it's up to the reader to filter and translate most of it from the pitfalls aforementioned into something more to the center of the bell curve.