Programming Books

This book is a quick way to get up to speed on C# 2.0. Highly recommended for developers new to 2.0. My only complaint is that it neglected to mention the new SqlBulkCopy class, an important addition to ADO.Net.

I've had this book for almost two years now, and I consider it (along with Liberty's classic "Programming C#" [I have both first and second editions]) one of the most useful books for helping me move from "beginner level" C# to "journeyman" mastery of what has become my favorite language and daily working tool of choice.

Liberty's books join with my books by Sells, Petzold, Gunnerson, Archer on that small shelf ... within arms reach ... which I consider essential tools to have as I work in Visual Studio.

What I find unique about "A Developer's Notebook" is :

1. Content : the sheer amount of immediately useful information and code samples. This is a book, imho, for people who've already reached initial mastery of .NET, and are ready for intermediate-advanced topics. There's more technical content, more information, "per square page" in this book than in many books on .NET and C# that are 800+ page "whoppers" :) And I do have the sense that every bit of code in this book has been "refined" to the efficient minimum without losing its "educational punch."

2. Book Design : imho the design and structure of the book are a "tour de force" of technical book design : it's in the form ... almost ... of a laboratory workbook; the "asides," or comments, in italic script font in the margin of the pages add a very useful commentary that evokes and provokes thought.

3. Immediacy : I get the feeling that Jesse is right there talking to me as he takes me through the intricacies of IEnumerable, Generic Interfaces, Delegate Covariance. Very good terse introductions to technologies like ClickOnce.

4. Technical Format : the book has a format of presenting a concept concisely, outlining the structure of the classes or methods involved, describing a practical usage scenario, and then, in a section titled "How Can I Do That ?," presenting a key code example that demonstrates the technique in use. I find this similar to what I perceive as the "experimental" method in Petzold's books, and, for me, this is a compelling way to learn.

4. Writing Style : As in JL's other books, I personally experience him as one of the clearest writers of technical expository prose I have ever read. In sections typically titled "What About," or "How Can I Learn More," for each major topic, he succinctly addresses questions that imho any intelligent developer might be asking about the limits or side-effects ... or the "gotchas" ... of the techniques presented.

I like to compare learning a programming language with learning a musical instrument. It seems to me that initial mastery of C#, like learning to play the guitar, involves a required period of just learning the general way you use the tools (the Visual Studio environment, the .NET compiler, assemblies, WinForms, Classes, Interfaces, UserControls) : until you have that initial "vocabulary," imho, you can't really "play a tune." But once you do have the initial comfort level and mastery of the tools, you are ready to start with studying simple "Etudes" which are designed to be musically satisfying in themeselves and, at the same time, help you progress in mastery. Using that analogy, I consider "A Developer's Notebook" a book of "Etudes," an excellent one !

In summary : this is one of the best technical books I've ever read. I do hope that at some point JL will do another book in this format, and structure, probing, in the same "experimental method" other topics in .NET 3.0 and 3.5 like LINQ, sophisticated uses of AppDomains and Contexts, the ability in WPF to get WinForms controls across domains, etc.

best, Bill Woodruff
dotScience

I purchased this book to get prepped for 2.0 development. As usual , Jesse delivered with additional benifits. He is a great, clear speaking, author. I needed the facts and he delivered.

Well worth owning for those of you transitioning from 1.1 to 2.0.

This is a very good "delta" book for moving to 2.0. It doesn't spend a lot of time with "object oriented programming began in 19..."-type gibberish. Instead it moves directly to some of the new features and talks to you like you know what your talking about.

Easy read.

However, the introduction says something to the effect of "this series skips the 'hello world' applications and is instead the often frantic scribblings of real developers performing real tasks" or something like that. In reality, none of the examples was terribly realistic. It was the same type of examples and 'hello world' demonstrations you would find in any other book. And the "scribblings" in the margins were often just pullouts from the text--just like any other book.

Overall - good book. But the marketing hype for the series is just that--hype.

I just borrowed this book from the library as I'm trying to cut down and only buy true reference books. I didn't have a whole lot of expectations, but this book was exactly what the doctor ordered. I knew C# for VS.NET 1.1 and am gradually migrating to 2.0 and all of it's extra features. I just wanted a book that covered the new stuff... and could come as close to just injecting the information into my brain without all of the extra fluff. This book does exactly that. If you're new to .NET don't get this book... but if you're looking for an incremental upgrade book (as I was) that is concise, full of examples, and covers the whole spectrum of VS.NET 2.0 then this is IT! That said, the title is just a bit misleading... the first chapter is about the new C# keywords and constructs, but this book covers changes with Forms, ASP.NET (Themes, Master Pages, ...) and so forth. This books has been hard to put down and I'm seriously considering buying this one to add to my reference collection. I've learned a lot from it in just the past 24 hours.

It has been a couple of years since I read this book, but I'm sure most of it is still relevant. It's definitely one of the first books you should get if you're interested in web analytics. It's one of those books you can go back to and use as a reference when you need valuable input.

I bought this copy and Web Analytics Demystified. This book repeats a lot of information in "demystified" plus it gives you coding tools to build your own metrics. More bang for the buck here.

Companies are looking for more and more business intelligence from their Web sites, both to improve their marketing efforts and determine ROI. This is a good thing. This is an exemplary "how-to" guide for Web Analytics. Extremely useful.

I think that the book is for differente people: programmers and marketers. But I found it quite interesting althought you have to select what hacks are appropriate for your job.

Web Site Measurement Hacks is the best book in the Web Analytics field. The book explains introductory topics as well as the most advanced ones in a chronological natural way. Subjects like what is web analytics, how to choose a vendor, how the technology works, and how to implement a web analytics program in your company are covered extensively.

Besides being well written and almost encompassing, it presents also the point of view of several of the Web Analytics' experts and vendors. Many of the Hacks are co-authored by big names, such as:

* Bob Page (Yahoo!)
* Bryan Eisenberg (Future Now)
* Jim Sterne (Target Marketing!)
* Jim Novo (Drilling Down Project)
* Jim MacIntyre (Visual Sciences)
* Jason Burby (ZAAZ)
* Brett Hurt (Coremetrics)
* Xavier Casanova (Fireclick)
* Jeff Seacrist (WebTrends)
* Akin Arikan (Sane Solutions)
* Jay McCarthy (WebSideStory)
* John Marshall (Clicktracks)
* ... and many more!

The index is very helpful and you find subjects very easily. The book is well organized and I refer back to it every time I have doubts. It works for me as a Web Analytics' Encyclopedia.

This is another phenomenal book from Craig Johnson. This one takes us back to Wyoming, and to Walt Longmire's experiences in Vietnam. And, the two are related. As the story unfolds, you understand the relationships between a case in Vietnam regarding a drug dealer and a case in Los Angeles... Well, I'm not going to hint the ending because it will ruin this book for you. Because, as usual, what makes Craig Johnson's books so good are the twists in the story and the larger than life characters. In this book, there is still of course, Henry, the "Cheyenne Nation". But, then we also get to meet Virgil and the "Crow contingent". It's that sort of Western humor that keeps bringing me back to Craig's books and also it's the story line and the characters. I highly recommend this and every book of Craig Johnson's and I look forward to his next one.

Walt Longmire, the sheriff of Absaroka County, Wyoming, finds himself in the midst of a mystery derived from his service in Vietnam around the time of the Tet offensive. A young Vietnamese woman is found murdered near the interstate with Walt's picture in her purse. The picture was taken at a bar during the war and shows a woman with whom he had been friendly. The murder victim resembles the woman in the photo, and Walt thinks that perhaps she is that woman's granddaughter.

So much for the beginnings of the mystery. From that point, the novel progresses on two planes, juxtaposing memories of Walt's experiences in Vietnam and the investigation into the murder. It is a richly rewarding tale, with haunting memories of the Vietnam War, with Walt having to solve two mysteries separated by 40 years.

This novel is the fourth in the series and the Wyoming setting is certainly different from most other mysteries. The inclusion of a ghost town may be symbolic--the ghosts of the past continue to haunt the present. Written sparingly, but forcefully, the tale is gripping, and the book is highly recommended.

"No matter what aspect of law enforcement with which you might be involved, there's always one job you dread. I'm sure at the most complicated venues it's the terrorists, its serial killers, or it's gang-related, but for the western sheriff it's always been the body dump. To the north, Sheridan County has two unsolved, and Natrona County to the south has five; up until twenty-eight minutes ago, we'd had none. There you stand by some numbered roadway with a victim, no ID, no crime scene, no suspects, nothing." (Page 15)

If you haven't read a novel in the Sheriff Walt Longmire series written by Craig Johnson you have missed a real treat. From "The Cold Dish" to "Death Without Company" and the previous novel, "Kindness Goes Unpunished" the author has developed not only a fascinating and complex hero in Walt Longmine, but numerous secondary characters that are just as alive and vital as Walt is to readers. That continues here with his latest release "Another Man's Moccasins" which begins two months after events depicted in "Kindness Goes Unpunished."

Sheriff Walt Longmine has returned home to Wyoming and is dealing with the personal and family repercussions of recent events as best as he can. Progress is slow, but steady. At the same time, the recent events have triggered in some way flash backs for Walt of his time in Vietnam shortly before the Tet Offensive in 1968.

The discovery of a Vietnamese woman in a ditch doesn't help his contemplative mood or his ability to ignore the past. Summer in Absaroka County is supposed to mean vacation season with folks coming to the rodeo. It isn't supposed to mean death. The woman was strangled at first and then whoever did it squeezed her neck too hard and broke it, before dumping her lifeless body in the ditch. When Sheriff Longmire checks the nearby culvert he is attacked by a violent homeless man who also has the dead women's purse. In that purse is a picture of a much younger Walt Longmire, playing a piano half a world away in a bar in Vietnam. A picture that includes a woman who worked in that bar and who bore a striking resemblance to the dead young woman found in the ditch.

With a flashback for nearly every step forward in the investigation, this novel serves to not only tell an interesting contemporary story it also fills in a major part of the Walt Longmire's life long before he came home and started his 24 years and counting Sheriff's career. Another election is coming and this is a novel where Walt is not only feeling his age but also finding that so much of his personal life is no longer under his control. The past is never truly past and Walt is attempting to put it back in its tiny compartment and failing because of so many reminders.

Readers that expect the body to fall in a prologue or certainly by paragraph 3 of the first page because that seems to be the rage these days according to writer's magazines and some publishers will be disappointed as the body doesn't fall for about 15 pages. Readers that hate flashbacks will be annoyed as the secondary storyline flashbacks number in the double digits and begin before the first body drops.

However, readers who like series featuring characters that become part of the family, books that build on top of each other building depth and life to characters in arcs that carry from one novel to the next, and books that showcase characters that evolve will love this latest novel of the series. Once again Craig Johnson weaves a tale full of the best of people in a morality play set against the backdrop of the Big Horn Mountains.

"Another Man's Moccasins" is another very good read in a series that is overall very good. Reminiscent of the work by James Lee Burke regarding descriptions, the effect here is just as good and yet at the same time different with Craig Johnson's own edge. While James Lee Burke's work these days is pitched against the backdrop of Hurricane Katrina, Craig Johnson's work remains focused more on the basic notion of good and evil and at times, the plight of the American Indian. Unlike Burke who let his editorializing dominate recent releases to the detriment of the story, Craig Jonson consistently puts story first and anything else secondary.

The result is another very good read and one that needs to be read after "Kindness Goes Unpunished." I would recommend reading the entire series in order if these books are new to you.


Kevin R. Tipple (copyright) 2008

Sheriff Walt Longmire is back on the job in Wyoming and anxious to help get his daughter Cady back in shape after her accident back in Philadelphia. Walt has brought her home to recover and she is gaining back her strength and her memory, although it is slow going.

Walt's attention is taken away from Cady when he is called to a scene where a Vietnamese woman's body is found alongside the interstate. When Walt goes to investigate a nearby culvert he discovers Virgil, White Buffalo, a homeless Crow Indian. What part, if any, Virgil played in the death of the young woman is something that Walt is determined to find out. Walt's gut feeling is that Virgil was not involved in the murder but he takes Virgil into custody until he can get further into the investigation.

The young woman that was murdered reminds Walt of his time in Vietnam and the story goes back and forth between the present time and Walt's time in the service. Henry Standing Bear, Walt's good friend, spent time in Vietnam with Walt and is now spending time assisting Cady in her recovery as well as helping Walt work out all the unanswered questions presented by this murder. Henry seems to have the ability to bring up questions that Walt really does not want to hear-and this makes for some interesting conversations.

Craig Johnson's books have been very successful and this one is probably the best so far in my opinion. I love the characters and Virgil White Buffalo is someone I won't soon forget.

Armchair Interviews says: Craig Johnson has done it again.

I loved the first three Sheriff Longmire series but I think this one fell short. Too much in Vietnam and too much foreign language, the new charachters were slightly flat, and I am hoping that the next book will be more in the line of the first three. Disappointed.

This book gets five stars, because from the first time I picked it up, it helped solve a problem I had at work with a highly annoying colleague who constantly went over my head to report to higher management anytime she even suspected I or a member of my team might be doing something wrong or not the way she would do it. Resorting to outright lies and spreading office gossip was not below her. Asking her to stop, being nice to her or being angry with her did no good. By following some of the advice in this book I was able to start to turn things around within a single day.

That is the really great thing about this book, it provides practical advice from experience project managers not only about tools and methodology of managing projects that work, but also the pitfalls of office politics and how to successfully deal with them.

The methods and tools presented in this book are very good, and are what the authors have found works in their projects. You might find that some of this is not applicable to you if you work in an organisation that already has an established methodology, or if the client insists things are done a certain way. It certainly presents some new ideas and tools to try that might improve your current proccess.

Another great thing about this book is its simplicity. There are many techniques for everything from project estimation to software testing, some of which require a high level of expertise. The techniques presented here are ones that are simple and easy to implement.

It is always good to learn from other peoples success, and this book gives you an insight into how its authors successfully manage their own projects that is valuable to every project manager.

I bumped into this book by way of "Head First PMP", also written by Stellman and Greene. Because I liked the PMP resource so much, I thought I should give this book a chance and I was not disappointed. Packed with useful information, case studies and examples, this book is a resource any technical project manager will want to have in their collection.
One bonus I did not count on was the companion website which includes downloadable templates, PPT slides and other electronic assets.

Highly recommended!

This is a nice book, everything about it is so neat and nice. I am glad I purchased this book from Amazon.

Applied Software Project Management
Reviewed by Steven D. Sewell, PMP
Project Management Institute, Tampa Bay Chapter

Having been peripherally involved as a software release project team member in the past, I knew enough to get my piece of the puzzle delivered. The information in this book allows me to broaden my perspective and actually comprehend the picture I see on the puzzle box cover. The book is written in a straight ahead manner. If you are one who like examples of what is being discussed, then this book is for you. The use of clear definitions makes each topic understandable and the analogies make them memorable. Tables and scripts are used throughout to exemplify each tool and technique. Most useful in practice are the sections that aid in the diagnosing of problems that can be encountered. This book definitely hits its goal of delivering a practical guide into the hands of a software project manager. The only improvement would be to have "handbook" or "guide" placed somewhere on the cover.

This book covers concisely all the modern aspects os software project management, without the complexity found in more formal PM sources like the PMBOK. Moreover, the job of translating the broad and general concepts covered in the PMBOK to practical day-to-day scenarios is the major benefit from buying it. It won't, however, cover an specific issue like estimation to the level that enables you to be an estimator (this subject, for instance, is only 17 pages long), but will provide you the guidelines and references to additional material to do so.

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.

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.

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 think Rajesh has done a significant amount of effort and studies to explain the Vista gadget in his book. Before reading this book i had little info about the vista gadget but after reviewing this book I have gathered all the technology and the programming aspect of Gadget. The way Rajesh has added the example and explain the impact of the gadget in the real world is just awesome. The way good and bad gadget explanation and about choosing the design for it is absolutely perfect. This book covers most part of Gadget programming for windows vista.

Although it requires lots of practice and knowledge of different technologies to create gadget but this book tries to cover most of the technologies involved.

I would definitely suggest my friend to have a look into this book.

This book is very simple to follow, and there are variety of useful examples. A great start for gadget developers. If you want to create vista sidebar gadgets, this is the book. Your skill-set doesn't need to go beyond familiarity with HTML, CSS and JavaScript to use this book. I have read other books most of the time the examples don't work, but this book is different, all examples just work. I can say simply great book for creating gadgets and an excellent read.

Easy to understand and written brilliantly. I was able to create my vista gadget in a day.

There are numerous gadget examples which are developed through out the book. I particularly loved the Comic Strip Gadget included in the extra section of the book, that one gadget is worth the price of the book.

I am beginner to Vista gadgets and I found the book to be explanatory with lots of examples. The book explains design, architecture, deployment etc very efficiently.
Gadgets development is very interesting for me now. I would definately recommend this book to my web designer friends.

This is awesome book with in-depth analysis and great reading material. User friendly explanation that is even good for the starters. The book contains many topics that give detail orientation of learning and implementation. This book has very comprehensive details that explain everything and require no further explanation. 200% worth reading!!!

While the early chapters go overboard with meta-meta-meta-data, the latter chapters are truly exceptional. Hoberman's experience doing data models at many firms shows through here, which translates into truly smart advice. Chapters 8 and 9 are gems, and should be required reading for all data modelers.

I loved that book since it is full of practical advices and really justifies its goal of being Modeler's workbench. I use this book often in my daily data modeling practice.

I have less than one year of data modeling experience and I thought the whole book was a great read, but I got the most out of the discussion on Abstraction in Chapter 9. After reading this chapter, I feel I can spot opportunities to make my modeling structures more flexible. Definitely recommend this book.

I like the way Steve uses analogies to help us better understand modeling. His introductions to each chapter are both amusing and a great intro to the subject matter in each chapter. His creative way of introducing techniques and the innovativeness of the techniques themselves have had a large impact on the way our department does data modeling. There are two books every data modeler must own: This book and Data Modeling Essentials by Simsion.

I just finished reading the Data Modeler's Workbench cover to cover. It is an excellent piece - or as Steve would say, a great story!

I wish I had read this when I first bought it years ago. It would have really helped my modeling career - and I've been a modeler the past seven years.

I think this book is a must read for modelers of any level - from start to finish, not skipping chapters. It nails requirements gathering and analysis, providing templates for capturing same, recognizing that is where the most work lies. I really like the normalization hike and analogy to hiking to the highest peak, then denormalizing and/or abstracting.

It is not a book on theory written by some college professor or glorified lecturer that never or rarely worked in the field; rather, Steve is a tenured data professional who took the time to write down how he does it successfully. Why reinvent the wheel or proceed along in a haphazard way when he lays out how to do it?

Steve also has all the templates on his website, which is a big help.

If you are coming from mainframe DB2, this is the book for you. Phil Gunning does a great job of explaining the many parameters and settings that make up DB2 UDB. Explanations are clear and straight to the point. It helped me to understand the DB2 UDB architecture and to get up to speed quick.

This book has helped my get started on monitoring and tuning my databases. Coming from Sybase, I had no idea where to start. I picked up this book and it guided me through all the monitoring setups and provided a monitoring and tuning methodology -- along with recommendations. This stays on my desk and is very handy.

This book is really well organized. The section on logical and physical design was a good review for me. It reminded me how important a good design is to a successful database implementation. The SQL Tuning, Buffer pool tuning, and DB and DBM CFG tuning chapters have helped me take care of my problem databases and suboptimal SQL.

I found this book to be very useful in tuning SQL and bufferpools. I liked the chapter on Problem determination and the utilities section. All v8 utility enhancements are provided.

The chapters on Type-2 indexes and MDC really helped me better understand how type-2 indexes improve performance now I understand what a dimension is and how to identify good candidate dimensions. The chapter on buffer pool tuning and Sort along with the DBM and DB CFG tuning tips have helped get my boss off my back!This is a great book by a DB2 Consultant.

One of my Junior Engineers asked me some months ago about my process for debugging. This book gave him a much better answer than I did at the time. It pretty much exactly summarises everything I have learned in over ten years of embedded software development, and presents it in a very readable and compelling form. Highly recommended for all levels of developer.

This is an excellent book on debugging. Whether you're debugging mechanical systems, electrical circuits, or software, the methodology presented is extremely practical and systematic. The author presents nine debugging rules that can be applied to any problem. The text is well-written, engaging, and humorous. The author also included a wealth of war stories that are worth the price alone. Highly recommended.

Quite liked it. I now have a game plan for approaching bugs in a nonrandom manner (including intermittent bugs):


Understand the System
- Read all related documentation
- Draw a system diagram and understand how things are connected
- Know the capabilities of your debugging tools


Make It Fail
- Start from a clean initial state
- Consider automating lengthy steps
- Make it fail in situ; don't waste time simulating the environment
- For intermittent bugs: list possible factors and try varying them one at a time; output a logfile and look for patterns


Quit Thinking and Look
- Watch it fail
- Use Remote Desktop / VNC
- Add logging and monitors
- Don't start thinking until you've limited the number of possible causes


Divide and Conquer
- Binary search
- Use test data with an easily identifiable pattern
- Start at the failure point and work backwards
- If you discover other bugs that may be related, fix them before continuing your search


Change One Thing at a Time
- Don't panic
- Back out changes that have no effect
- Compare the logfile with that of a good system
- Check earlier versions


Keep an Audit Trail
- Keep a detailed written log


Check the Plug
- D'oh!
- Have the components been properly initialized?


Get a Fresh View
- Try explaining the problem to someone (or something)
- Ask an expert: co-workers, the vendor, documentation, bug database, the web
- Report symptoms (including possibly unrelated observations), but not your theories


If You Didn't Fix It, It Ain't Fixed
- Fix the root cause
- Make the problem happen again by undoing your fix

I worked with Dave Agans for over 10 years and I can tell you first hand the man knows what he's talking about. From developing hand-held controllers in the late eighties to single-board OS/2-based videoconferencing products to software collaboration tools, we have debugged problems of every ilk. Whether the problem was an FPGA bug, a faulty component in a board, a race condition in a device driver or a dangling pointer in a DLL, Dave always approached the problem with his same set of debugging rules, and they never let him down. Read this book. It's engaging and fun to read. But more importantly it will make you a better debugger, whether you're debugging hardware, software or your lawnmower.

This book is absolutely indispensable for anyone working in any job where things occasionally work in an unexpected manner. It's concise, funny, well-written, and full of immensely useful tips on how to go about debugging problems.

One of the great things about this book is that it's generalistic in nature, not specific. Agans's decades of troubleshooting experience has given him great insight on how to go about debugging in all sorts of environments, so he lays out nine rules for approaching any problem:

Understand the System
Make it Fail
Quit Thinking and Look
Divide and Conquer
Change One Thing at a Time
Keep an Audit Trail
Check the Plug
Get a Fresh View
If You Didn't Fix It, It Ain't Fixed

[...]

Debugging isn't an art performed only by folks with some odd genetic disposition, it's a critical craft which can and must be learned. I was fortunate to have some good troubleshooters as mentors during my days working radar inflight in the Air Force, but I've fallen out of many of the good practices those folks beat^H^H^H^Hinstilled in me. Agans's book is helping me pull out of the thrash and churn mode of debugging.

This book's only 175 or so pages long and is well-worth adding to your library. Actually, substitute "a critical addition" for "well worth adding". I'm also going to make sure this book gets added to the professional development reading list I'm working on creating.

I don`t speak a lot english and i was so scare to buy it because this guy is brithis but i saw some reviews and took the risk. when i got the book we can resume in one ward i was just surprised, it is completly amazing, i dont know for one else but for me this guy that`s really knows how to explain the difficult world of 3D, Thanks Peter Draper I've already found the key to my goal "this Book"

Most books out there are rehashes of the help documentation or popular tutorials already out there. For this book, however, almost every single tutorial covered tricks and techniques that I've never been exposed to before in my years of working with 3D Studio. Definitely an eye-opener for anyone who wants to learn how to create any sort of realistic environmental effect.

This is one book that is a must-have.

Most 3D books are unimpressive to me-- the sorts of things that could be readily learned by reading the manual or help files (particularly in the case of 3D Studio, which has excellent help and tutorials.)

Pete Draper's book is one of the happy exceptions-- it extends one's knowledge and capabilities, and moreover, his work is excellent; these are images and animations that would get you a job, if you could make them.

Would that there were more books of this calibre!

I have had this book for about 2 months now and all I can say is wow. This book has really been helpful...extremley helpful I must say. Easy to follow, the tutorials ALL work....Pete draper expresses all aspects of each tutorial and explains the WHY factor in each step in his tutorials. I cannot praise this book high enough. It has solved a lot of underlying problems that most would use plugins to work around. I give this book a 100% feedback....and I really hope he launches another...I will definatley buy the next one.

There is a reason why the used books are priced the same as the new for this item. This is an essential buy. Beginners should try get their hands on something a little easier first, but everyone with even a little bit of experience needs to get this book. Whereas many books leave you with a feeling of being "rushed" or of not being properly thought out, this one leaves you with an impression of having every single tiny detail meticulously planned. The DVD even includes video tutorials that didn't fit in the pages of the book! And the author has a website for the book and users that have problems with the tutorials. And guess what? He actually visits the website and offers help! wow! what a concept!

The tutorials themselves are brilliantly planned. First, we get reference footage, that is analyzed in order to get the best effect. Then, Draper goes through each step, and EXPLAINS EXACTLY WHAT WAS DONE AND WHY IN EACH STEP. This is vital and is sadly overlooked in many tutorials from other sources.

What will he teach you? Exactly what the book promises: extremely realistic water, earth, air, and fire. This is done mostly through the powerful new particle flow system and multi-layer materials (I mean MULTI-MULTI-MULTI-layer materials here). After only a few tutorials, I my skills with procedural materials and particle flow increased exponentially.

An essential buy.