2 comments about Pro SQL Server 2008 XML (Pro).

1. I was amazed to see how well this book explain the concept of Spatial Data and all different techniques of loading and transforming XML from diverse format and systems. It shows so many examples at a very granular level. This book is a "must read" for everyone that has any interest on learning great powerful XML techniques on SQL Server 2008. It is definitely great!
   
   Rosa Lopez
   MS Information Systems



2. The Pro SQL Server 2008 XML book dives right into the details of XML from the first page. This book was written by a developer for developers, and the author goes to great lengths to demonstrate all the concepts presented in the book. In my opinion, this book scores highly in many areas.
   
   The author assumes a basic knowledge of SQL, but he thoroughly explains every step of SQL Server's XML functionality along the way. The book even compares and contrasts the SQL Server implementation of XML to the W3C and ISO standards, pointing out where the SQL Server implementation differs.
   
   However, while the book assumes this basic understanding, any developer interested in getting the most out of SQL Server's XML functions will find the book both informative and enjoyable. The author goes to great lengths to explain XML and why it's relevant in the database. This is absolutely the best reference for SQL Server XML that I've seen.
   
   
   The author provides what he calls "Cross-Platform Tips" at various points to call attention to limitations of the SQL Server implementation, or areas where it differs from the standards. These types of tips, generously portioned throughout the book, are designed to keep people from wasting hours trying to figure out why the XQuery code sample they copied from the Internet (or some other source) isn't working as advertised on SQL Server. While this book is written for SQL Server 2008, much of the functionality described works with (or is similar to) SQL Server 2005 functionality (as the author points out, some notable exceptions include the added support for Geography Markup Language "GML", and the FLWOR statement "let" clause). As the book explains, the difference between SQL Server 2005 XML functionality and SQL Server 2008 XML functionality is not nearly as large as the leap was from SQL 2000 to 2005. New SQL Server 2008 features aside, this book works equally well as a reference to SQL Server 2005 XML functionality!
   
   
   
   Another thing I like about this book is that the author builds on the code samples from one chapter to the next. There is a particularly detailed example of a hierarchical "bill of materials" that the author continually adds newly introduced functionality to over the course of a few chapters. He uses this example to demonstrate how to layer XML functionality to build an intricate application from a very basic premise. I really like the fact that this book provides examples and addresses the problems that most books go out of their way to avoid. Where many books give you a simple top-down hierarchical organization chart that's been done 100 times by 100 different people, this book gives you recursive XML Schemas. Instead of just rehashing the well-advertised SQL Server limitation that Document Type Definitions can't be used to validate your XML this book gives you working examples of code to get around the issue. The book provides many more real world examples, with some pretty intriguing ideas as well (like grabbing an XML RSS feed or searching eBay directly from SQL Server). A nice bonus: Almost all examples are designed to run directly in the AdventureWorks 2008 sample database, and all are freely downloadable from the publisher's website.
   
   
   
   And this book doesn't just stop at the server. The author provides analysis of client-side tools including LINQ to XML, SQLXML, HTTP SOAP Endpoints, and a wide supporting cast of XML support tools - many that are provided "out of the box" with SQL Server.
   
   
   This is the ultimate reference for all things XML on SQL Server 2008.

5 comments about A Practitioner's Guide to Software Test Design.

1. Lee Copeland's book, "A Practitioner's Guide to Software Test Design" provides an easily read introduction into a critical but often ignored subject. As those familiar with the IEEE Standard for Software Test Documentation (IEEE-Std-829) know, Test Design is the first step in turning the "What" of the Test Plan into the "How" of test execution. The IEEE Test Documentation lifecycle is Test Plan - Test Design - Test Case Development - Test Procedure Development - (Test Execution) - Test Summary Report creation. Many test engineers proceed directly from Test Planning into Test Procedure creation, and do Test Design implicitly as opposed to explicitly. This can have a negative impact on an effective test program. This book clearly shows how to implement the test design process described in Drabick's book "Best Practices for the Formal Software Testing Process".
   
   Lee's book provides a concise description based on excellent Case Studies of Black-Box (Requirements Focused) test techniques, moving from the simple (Equivalence Class and Boundary Value testing) to the more complex (Domain Analysis and Use Case testing). He provides the best description I've seen of test case development using orthogonal arrays. Lee then addresses White-Box (Structural Focused) testing, showing how to approach Control Flow and Data Flow testing. Again, he has the best description with illustrative examples of Data Flow testing that I've ever seen.
   
   Lee then describes two Test Paradigms: Scripted Testing and Exploratory Testing that appear to be significantly different, and shows how the two can be used together for even more effective testing. That's the way I've always done testing, by the way.
   
   His Defect Taxonomies chapter provides valuable insight on how to use such information in test design (I never thought of that), and he concludes with a short chapter that addresses the critical question When to Stop Testing.
   
   The Case Studies on "Brown & Donaldson" and "Stateless University Registration" are effectively used to provide valuable insight into the techniques.
   
   This book would be a good read in combination with the book from Rick Craig and Stefan Jaskiel, "Systematic Software Testing".
   
   In summary, this book is well done, is an easy read, and should be read by every test engineer.



2. Most texts on software testing have a chapter or two which describe test design techniques. This is the first text that is devoted exclusively to this subject. There is little in the way of theory. The text is practical and provides the software test professional with clear explanations and examples of test techniques that have been proven to be effective.
   
   Although Copeland covers both black box (behavioral) and white box (developer oriented) test techniques, the majority of the test design techniques described are black box. Each technique is explained along with its applicability, advantages/disadvantages, along with references for more information.
   
   For what can be a dry subject, Copeland effectively used humor to make this book very readable.
   
   I also appreciated the chapter summaries, key points in the margins, and a thorough works cited -- including several web articles. Highly recommended.



3. This information in this book is simply presented and very easy to apply.
   
   I think the price is a bit high compared to a related book (Systematic Software Testing by Rick D Craig and Stefan P Jaskeil). I managed to get the other book (536 pages) for about $40.00. While the other book represents much better value, I still bought this one and would do it again. If you can only buy one, I'd suggest getting Systematic Software Testing.



4. This is a great reference, giving a good overview of most common test methods. Good bases for in-depth study or to structure a class around.



5. I purchased this book to help me with a university unit primarily on system testing methods and techniques. Although this book covers many of the primary testing concepts needed for software testing, some of the concepts covered were sometimes completed short (or too verbose in some sections). All of the example questions after each chapter that were stipulated for the student to complete - answers were not provided either in the book, or online. So as a fellow software testing student, when completing some of the exercises, I was unaware of whether I was completing them correctly or not.
   
   However, on the contrary the book has some valuable information that I couldn't even find on the internet (when investigating some further explanations on particular topics covered).
   
   The book could have been written in a more professional manner, covering topics in more detail and exploring some of the minor (and major) difficulties that one can encounter when developing test cases for any software being created.
   
   It helped me with basic understanding of concepts. Further investigation on the internet was needed to get what I deem as "sufficient understanding" of the material covered.

5 comments about Linux iptables Pocket Reference.

1. This book is written for linux/unix sysadmins, not programmers. The topic of iptables is intimately related to guarding a network against intruders. A sysadmin task. Plus, the compact, pocketbook size lends itself to a common scenario.
   
   You're a harried sysadmin in the machine room of your company, surrounded by racks of computers and cabling. Equipment everywhere and little room for you to prop up a regular sized text on intrusion detection. Quite possibly, the master console is some cheezy old monitor that you got stuck with. Or even worse, it is just a terminal. If the latter, it's really awkward to do a man on iptables and also run it, especially if you're in real time mode against an active intruder. In other words, what this book is ideal for.



2. 'Linux iptables Pocket Reference' is an important and sorely needed reference to iptables, the interface to the Linux packetfilter used by System Admins to create firewalls, NAT routers, transparent proxies, and other 'magical' network devices. While not a tutorial, it offers good advice for those with a grasp of basic networking concepts, and a good notion of what a firewall is and what it is used for, in a dense and concise format. Sufficiently detailed information about the protocols involved obviate the need to keep additional references at hand, and make the work relatively self-contained. This should not be the first book you read about firewalls or tcp/ip, but if you are a networking professional, a technically oriented user, or just interested in creating special purpose network devices, this book belongs in your library. Those familiar with iptables will especially appreciate the lucid description of packet flow through the tables and chains, and the supporting diagrams ... they alone are worth the price of purchase.
   
   If you have need for a book on the topic, you will not be disappointed with this one.



3. Linux iptables Pocket Reference is a great book.
   
   there is a dearth of info on Linux iptables, and this pocket reference is a great book!!



4. Concise and very handy. Guides like these aren't meant to be a complete reference on iptables. Yet, the author managed to pack quite a bit into such a small book. 82pages from page 1 to beginning of index.
   
   21 pages to theory and operation -- connection tracking, accounting, NAT, SNAT, DNAT, Transparent Proxying, load balancing, and stateless/stateful firewalls.
   
   The next 61 pages are a command reference to iptables. It is in the command reference that you shall find interesting little nuggets like:
   
   1) How to rate limit incoming traffic. Specific examples provide for allowing only 10 pings per second.
   
   2) How to setup IP pools to match source and/or destination addresses. Instead of writing a line for each IP or netblock, throw the addresses into a pool and write a line for each pool.
   
   3) How to match multiple ports on the same line.
   
   and so on.
   
   Worth every penny. Lives up to O'Reilly name. Would recommend for every Linux sysadmin.



5. Last year, I was forced to become a fly-by-night system administrator. I worked for a small, local startup as its web developer, but was thrust into a sysadmin role when my boss decided to host a website on a server in our office. I was developing the site on our Ubuntu server, but was learning how to secure the server on the fly. This reference, out of all the other books I read and sites I visited, had the most bang for the buck.
   
   It's short and sweet. It describes what you should know, and gives you a reference for dealing with iptables syntax, and that's it. No flowery text, no colored pictures. Just simple "This is how to do X."
   
   If you're a sysadmin, especially if you're just getting your feet wet, get this book. It's cheap, it tells you what you need to know, and it fits in your pocket. What's not to like?

5 comments about Foundation PHP for Dreamweaver 8.

1. This is a good book. It teaches many useful techniques and how lots of "how to" ideas. However, the faux site that is created isn't goal oriented which left me feeling like the book was just a collection of random things to do. It seemed disorganized at times when you would or wouldn't create another page from scratch vs. revamping one you had already made. It was not always clear why you would be better to take one approach vs. the other. Setting up the localhost environment was somewhat confusing, though not too bad.
   
   I will definitely use it frequently. Good information, good book, good deal.



2. This man makes a promise of a written format that can be followed. The writtng is NOT CLEAR and leaves much to the readers imagination of to what exactly the format should be. There is no CD so that you can see how the step by step process works. He names his files but does not show the real differences between how he is set up and how you can set up to fit your needs. I waisted my money. He claims in the book there is support which at best is terrible.
   
   The worst book I have ever bought on coding. If I were you try another writter.



3. This is a very good book for learning PHP, and surprisingly, most of the examples work right out of the book as he's written them, which seems rare for a programming book these days. The projects that he has you complete are highly relevant to what you'd actually be doing with PHP, and that makes it even better.
   
   The only trouble I had with this book was that he sure packed a lot of information into each chapter, and he didn't use the sidebars as much as I would have hoped. It's easy enough to follow along with the examples the first time, but if you want to go back again and figure out how he programmed a small detail, you'll never find it unless you reread the whole chapter again. All it would have taken was a few little bullets here and there in the margins to point out some of the off-topic stuff that was going on in the examples, and the book would be much more functional as a reference. As it stands, I probably will have to get a whole new book for that purpose.
   
   Also, the support on this book is phenomenal. I missed a small detail in Chapter 6 that caused my script to fail, and when I posted on the book's message board, I had a reply from the author in less than a day. That's a really cool added bonus.



4. I am a frontpage user that has set up static pages in a web site. I needed to move from static pages to dynamic pages using a database. I couldn't use PHP with FrontPage so I switched to Dreamweaver and needed a book that covered both dynamic pages and Dreamwaver. This book walked me through setting up the environment to have Dreamweaver work with Apache, PHP, MySQL and phpMyAdmin. I am completely non-technical so these areas were beyond my comfort zone but the book walked me through it very successfully. It then took me through CSS styles, setting up an online feedback form, setting up my first database and tying it into Dreamweaver. It also showed how to insert, delete and maintain records in order to keep the database up to date. This was an excellent book for a non-techie as it didn't take any knowledge for granted.



5. This book is written very clearly and is really easy to follow. I've learned a lot of other really useful stuff than just the PHP content, things that I now realise I should have been taught by the official Dreamweaver 8 book, but weren't. The PHP content for which I bought this book is fantastic - much better than another generic PHP/MySQL I have read, as this is tailored to the Dreamweaver 8 environment which takes a lot of the guessing out of the equation. This book is written by and for people who use Dreamweaver 8 in a practical situation. I'm still less than half way through my book and already feel like I've learned much more than I expected. Highly recommended. I'll be checking out Mr Powers' other books when I finish this one. Thanks David Powers, you're a genius!

5 comments about C++ Pocket Reference.

1. For many years, I did most of my programming in C, but never learned C++. In recent years, I have been using Java mostly. Now I wish to get back to C++, and I have found this book to be an excellent introduction. In order to read this book one already needs to know how to work with the very low level aspects of C, and at the same time one must understand object oriented concepts. But for the reader who is at such a place, this book provides a very concise description of the C++ language. In just 125 small pages, the author manages to step through all of the aspects of the C++ language and concisely describe them.



2. If you are looking for a quick and dirty C++ pocket reference, this book should be on the top of your list. It covers all of the necessities, which is great for when you are switching between programming languages. If you have too many languages in your mind, a quick reference is a great little refresher, which this book certainly provides.
   
   My only qualm, and the reason it loses a star, is that the organization is not completely intuitive. However, after a few uses, you get used to this and it becomes a non-issue. I suppose you would have this with any book.



3. This book provides a quick and concise reference to the C++ language, covering everything from the basic structure of C++ files (including #include guards) and programs to variables and operators to the Object-Oriented features of the language. However, if you are looking for a detailed description of the C++ language, get The C++ Programming Language: Special Edition (3rd Edition) along with this book and you will have that plus a quick reference to almost all of the non-STL topics the other book talks about.
   
   On the down side, this book gives really superficial coverage of the STL, but then again this book isn't meant to be a pocket reference to the STL. For a good book on that, get a copy of The STL Pocket Reference.
   
   That being said, I would recommend this book to those who have either gone through or are going through their first year of programming courses.



4. This is a great C++ reference. After some years of mostly C and Java programming, I was able to review the language main points in a single day.
   
   It is a useful book for non-full-time C++ developers.



5. I have about a dozen of these pocket guides. I don't do C++ anymore but did many, many moons ago. My daughter is taking a C++ class now and I got this to help me remember C++ enough to help her with that class. It's all I need. In general, these pocket guides are enough for me most of the time regardless of the language or technology they are covering. Between them and google search, you can solve any programming task...

3 comments about Systems Analysis and Design.

1. Price reflects quality. This book is superb for System Analyst and Designers (SAD), both beginner and advanced ones. It is very informative that can be used for both learning and reference purposes. The authors explain everything very clearly using the same case examples (CD Selection case) and exercises for every chapter, so it's very easy to understand and keep track as you move chapter by chapter. I used to screw up in SAD but as I started using this book, I learned much more and much better than before. Thanks to the authors for thier good job and my professor who recommended this book to the class. Highly recommended for anyone interested in SAD.



2. I was introducted to this book as a student of DeVry Institute of Technology. I think the book provides the most concise, yet informative theory of the System Development Life Cycle. Those interested in project management, infrastructure management, etc. would find this book extremely concise and "to-the-point". The book also provides an array of examples, including case projects and questions. I think the only thing missing from this book is an interactive CD or software such as Microsoft Project or Visible Analyst. But we know how Microsoft is about licensing and purchase standards. Anyway, the book is an excellent resource for those interested in information systems management.



3. The third edition, copyright 2006, often seems outdated. The examples and references are usually from the 1980's or 1990's. The authors provided a new edition, but I don't see that much effort went into actually updating the material. They don't even introduce object oriented approaches until the last chapter of the book. It's almost like it's an afterthought. They also don't provide much information on RAD or agile methods.
   
   I feel like I bought a circa 1999 book. Disappointing.

5 comments about Learning C# 2005: Get Started with C# 2.0 and .NET Programming (2nd Edition).

1. I've been programming computers for 30+ years and have migrated across several languages and systems as times dictated. I have accumulated courses, degrees, jobs, projects, and rows of books along the way. My most recent focus has been Perl on FreeBSD and Apache/CGI/mod_perl. I now have the need to write Windows GUI applications. Unfortunately, Microsoft has not chosen to make Perl a first-class language on their platform, so I am left with few choices (I am most familiar with ActiveState Perl and Cygwin). Given the fact that Visual C# 2005 EE is a free download, I've decided to climb two more learning curves -- C# and .NET.
   
   When learning Perl, I found O'Reilly's "Learning Perl" and "Programming Perl" books to be awesome. So, I bought the C# parallels, hoping for a similar experience. Unfortunately, this has not been the case.
   
   The content of "Learning C#" is basically a subset of "Programming C#" by Jesse Liberty with advanced topics removed. Both are what I would call language survey/ "gee whiz" books -- they describe the "what" and/or "how", but often leave out the "why". I forced my way through both and may use "Programming C#" as a reference, but "Learning C#" will only collect dust.
   
   This book also fails its presumed purpose -- teaching the reader how to write good programs in C# at a basic to intermediate level. Mr. Liberty is clearly an intelligent person and a capable programmer, but, unfortunately, he and/or Mr. MacDonald are not good teachers (or, at least not for how my brain is wired).
   
   Both books suffer from a deeper criticism that seems to plague almost all Microsoft subject books. I cut my teeth on Kernighan, Richie, Pike, Rochkind, Plauger, Bach, McKusick, Wall, Schwarz, Christiansen, etc., and those are the standards by which I judge all others. The writing style and technical accuracy of those authors are levels above what I find from most Microsoft subject authors. My guess is that the C/Unix and Perl authors train to higher standards (e.g. Ph.D, post doctorate), their vocations require them to write to higher standards (e.g. academic and professional journals, peer review), and they have experience in education. In Mr. Liberty's defense, those authors are not subject to scope and speed of the Microsoft product treadmill.
   
   Given the lack of a good technical bookstore in my area, I am relegated to reading reviews such as this on the Internet, ordering a book sight unseen, and hoping for the best. Please post your reviews so we can help each other. :-)



2. This is a tough book to review because it addresses very remedial concepts in the C# language, as if being directed at new comers to the language, but the authors address these topics at a very high level, as if conversing with computer scientists. I believe this book will only appeal to the type of newcomer who's willing to wade thru the murky waters of remedial language theory; one who's not anxious to plunge into the deep end of quickly writing your own programs.
   I am a business owner who programs fairly in depth VBA programs for use in my own company, mostly in MS Access. I've studied Python and programmed some console applications, as well as remedial programs in wxPython. I have some anecdotal knowledge of ASP.net, Actionscript and some other tools. My goal is to write my Access applications with a more robust toolset (enter C#). So I'm plagued with an ambivolence of wanting to learn from the ground up but finding overly remedial or theoretical examples mind-numbing and inapplicable.
   I think this book falls into that category: too theoretical and remedial, even for newbies. I'm striking immediate paydirt with the O'Rielly book C# 3.0 in a Nutshell by Albahari. This book is also based on the newer version of C#. Albahari's book is very dense and terse, which for me is good--it doesn't dwell on concepts but gives you strictly the meat and bone with a spartan example. Allowing you to immediately grasp the fact and move on. Liberty's book (C#2005) dwells on and on with a topic and frequently spends a great deal of energy on topics of very low importance--Arrays are given an entire chapter (though not addressed until Chapter 10, half way thru the book). Yet arrays are, even by the authors' admission, the "least flexible of the five standard collection" objects. But the other 4 get short shrift in the 14th chapter on Generics.
   Don't get me wrong, I think it's a good book. I'm just not sure how to use it, since I'm not going to get a CS degree and I will never write a console application (which is virtually the only kind in this book). I couldn't easily understand the examples given for class inheritance, though I came to the book with a clear understanding of it. On the other hand, the Albahari book had clear and concise examples by page 14.
   Again, I'm not trying to knock the Liberty book. Only trying to give my experience of it, for those who might describe their programming experience or focus as I do: I'm not truly a newbie; I undertand OOPs and have some skill with other, albeit simpler, languages; I want to program specific applications now; I have a limited tolerance for long theoretical explorations on the language. If you're like me, you might find more lean-meat in C# 3.0 in a Nutshell by Albahari.



3. This was the first book on learning C# 2.0, and while at first I enjoyed the book, when the author started discussing more advanced topics like delegates and events, his examples, I felt, were overly complicated and often left me agitated trying to figure out why he programmed the examples the way he did. After reading other C# 2.0 books, I realized just how bloated the author's examples were. Anyone interested in a beginner C# 2.0 book should try Herbert Schildt's book, The Complete C# 2.0 Reference. His examples are concise, performing as much as necessary to convey the topic Mr. Schildt is currently discussing.
   
   I felt it necessary to write this review after encountering many instances online and in print of people suggesting this title, and my adivce to someone about to purchase this book is to shop around. There are better alternatives than this mediocre book. I especially encourage you to look at Schildt's book if you are new to C#. Charles Petzold even has a free C# 2.0 book (pfd) on his website that does a decent job explaining the .NET framework.



4. This is an excellent book on C#. I use it as a reference all the time for my ASP.NET dev. It's almost as big as the Learning C# book by the same author.



5. I've read the high reviews for this book that's why I bought one, but eventually got disappointed with the lack of depth on explanations esp.regarding OOP. I suggest that beginners get a different learning reference. Jeffrey Suddeth's book is compact yet organized and topics are well-explained, but you must supplement that with other books as well.My experience is, you won't learn so many things in just one book, you need 2 or 3 while learning. I have yet to review Andrew Troelsen's book which is forthcoming. If you happen to find one that explains in detail the important topics like generics, collections, events and delegates and OOP, please help others by posting your review. Thanks

5 comments about Core Java(TM) 2, Volume I--Fundamentals (7th Edition) (Core Series) (Core Series).

1. I have an earlier version of this book and would love to get a Kindle version for reference. But... You save $3 by getting the digital version despite the fact that there is no shipping, storage, or printing costs?
   
   WTF?
   
   At $10 a piece I'd love to fill a Kindle with dozens of coding reference books that are filling up my library, but at $30+ a piece it's just not worth it.



2. I only wish the authors would have understood that it's better to write variables and declarations first and then use them later in the code. All the code examples are funnily written with the use of the variables first only to wonder from where they come from and later to realize that they're are at the end!!!!
   
   Also author has tried to pack too much of details which can be halved.
   Herbert schildt is a better option.
   
   But still the books is readable for beginners.



3. I have an older version of this book but it covers many of the core features of the language. This is a good book if you are looking to start
   programming in Java.



4. This is my favorite Java book. Although I have a background programming in C++, I find many of the other Java books to be cryptic or assume you wish to develop for the web. This book is straightforward and easy to read. I especially found the comparisons between Java & C++ interspersed throughout the text to be helpful.



5. I read this book years ago (I guess that was the first edition). I am ordering a replacement copy today, even though I am no longer an active programmer, because it is so good. It is one of those rare textbooks that you can actually read from cover to cover, like a novel.

5 comments about Pattern-Oriented Software Architecture Volume 1: A System of Patterns.

1. This is an unusual book in the pattern genre. It presents a number of patterns, categorized by archtiectural level. That's just the first part of the book, though. The third of the book is about the process of using, relating, collecting, and distributing patterns.

   Only chapter 2 really addresses patterns for the strategic, architectural level of a software system. It does a very adequate job, using a variety of notations, examples, and analysis steps. This book is from 1996, so time has changed our view of some patterns. "Reflection," for example, has become pervasive in applications based on plugins and software components. It is also a fundamental API in the major langauges (Java and C#) released since this book was published - perhaps reflection should be downgraded to an "idiom". That's just nitpicking, though, since reflection is even more important now than when the book was written.

   For contrast, the authors present additional design patterns (including some from Gamma's book) for use at tactical design levels. They also discuss idioms patterns that typically involve just a few lines of code within on function. The contrast between the three different levels of implementation and design gives a useful discussion. The authors also present a weak chapter on "systems" or "langauges" of patterns The discussion is OK as far as it goes. The weakness is in what it omits. After reading this brief chapter, the programmer has very little practical information about choosing patterns from some library for some task. The poor programmer has no information at all about how to link patterns together, and that's a real stumbling block for beginning pattern users.

   The final section of the book is really sociology. It's about the pattern community, what that community is for, and how to be a working member. I find the discussion un-helpful, but I expect opinions to differ.

   Even today, this is a good second book (after Gamma's 'Design Patterns') on patterns and pattern usage. It lack the depth and precision of Gamma's book, and tends to add words without adding meaning. On the positive side, it's broader than Gamma's, and addresses a wider range of implementation levels.




2. First of all, you need to understand the patterns in the gang of four book before you attempt to read this one. They talk about them all over the place without explaining them. That's a warning, it didn't affect my review.
   
   The major thing I don't like about this book is the abstractness with which they talk. They give you a high level description of a pattern and leave you with that fogginess.
   
   I think the examples were poorly chosen. I would have prefered to have examples that are only as complicated as they needed to be. Unfortunately the book uses examples like, "We're going to make a voice recognition application" or "We're going to make an OS that can run applications that were built on Unix or WinNT or Linux". I think the intent was to have some real-world-I've-been-working-for-six-years examples... it would have been smarter to put the real world examples in a separate chapter and keep the design pattern explanations simple.
   
   Also, I hate the diagrams. They should have just copied the diagrams in the GoF book! Instead they chose these diagrams that give less info and IMO are downright ambiguous in some situations. Another thing the GoF book does is have 2 separate diagrams, one that's a (simple) real world example and another that's a diagram of the actual pattern. This book only has the diagram of the actual pattern.
   
   I disagree with those that say this book is better than the GoF book. I think what they like is the material covered. Material aside, the GoF book presents the information in a much clearer way. That's why I prefer the GoF book over this one.



3. Second best isn't bad when the #1 book changed forever the way software architecture is talked about. GoF is not only well-written, but it covers all the basic, most-used patterns. Everybody thereafter is going to have to either re-hash GoF, criticize it, or come up with new patterns which are not as fundamental.
   
   This book is full of new patterns, and fortunately they are good ones: Command, Broker, Layers and worth the price of the book in itself Presentation-Abstraction-Controller.
   
   PAC can be seen as a generalization and extension of Model/View/Controller. The Abstraction is the domain-specific part of the architecture, effectively the Model. The Presentation exposes the Model in some interesting way, either as a user-interface in which case it is a View, or as an API, in which case the Presentation becomes a new Abstraction used by the next level up. The Controller is left with the job of coordinating the Presentation and the Model. The key to the pattern is that PAC agents can be built up into layers with the Presentation API of each lower agent creating a higher abstraction for the next level. Thus PAC becomes MVC for all or your architecture, not just the UI.
   
   The book goes into this at length and adds useful discussion of MVC. Highly recommended.



4. A lot of the reviewers have said that this is the #2 best book about patterns : just trust them. I have bought it with the hope to learn more about patterns, finally it has given me a larger point of view about the subject and has improved a lot my creativity during software designing processes.
   
   If your new to patterns just read the GoF, then buy this one. I think you will then have a nice knowledge about the subject.



5. This book uses an easy way to explain system patterns. I think every software developer has to read this book; it's a nice reference to help software architects doing a well-done job. Another great reference that you may have in your list of references is the classical book "Design Pattern", also at Amazon.com.

5 comments about The Art and Science of CSS.

1. I've bought and already finished to read this book.
   
   I'm a interface developer with a good background into CSS and XHTML; i think that this book was not written to somebody interested into the fundamentals and step-by-step of the CSS.
   
   It's a collection of code-based insights (for each chapter, 2 or 3 progressive explanations) from the authors; it's amazing if you (like me, when i bought it) are searching for some inspirational examples, relying on standards to achieve impressive visual results.
   
   This book also encloses some aspects of CSS 3, and how it will unequivocally improve the standards-based design, with things like multiple backgrounds, table pseudo-classes, and others, even before the integral adoption of this standard into the mainstream browsers. It put the reader one step ahead, acknowledger of the future possibilities of CSS.
   
   I highly recommend this book. But if you are searching for something less visionary and more instructive, you'll need to search other options.



2. The Art & Science of CSS is a good book if you looking for creative ideas or inspiration for CSS but while the book says all you need to is some familiarity with HTML, you do need to know some basic knowledge of CSS. This book would be a good addition to you web design library but only after you learn the basics of CSS from another book.



3. There are many excellent tips and workarounds offered in this book. I have been working with CSS for a few years now but as it is a moving technology, one can never be "ahead." The authors do a good job of bringing newer tips and tricks forward along with offering some useful workarounds for cross-browser issues.



4. I think there are many books that cover this ground a lot better and cheaper as well. Friends of Ed actually has a couple that I would recommend before this. And most certainly Bulletproof Web Design by Cederholm.
   
   This book is really light on details and light on content. It's not at all worth its price, and it's only covering the very basics in a small number of areas. This is definitely not one of the first books you should be looking at about CSS.



5. I really like this book. It is EXACTLY what I seek in a design/development book. I want examples, code and explanation. Nothing more.
   
   I've been doing this stuff for 7 years, so much of this wasn't particularly new to me, but the value is in seeing what experts think (and why) and then taking what you want from it. No cruft; just good solutions.
   
   My only gripe is that it could be considerably longer. The book covers 7 topics really well. I'd like at least 10 more, please. I'm sure this is the most common complaint. Additionally, I could do without the fancy book layout design, but I guess it doesn't hurt.
   
   Definite value here. It's next to my desk all the time and I use almost all of their techniques in my projects. It's disappointing that more publishers don't create this kind of book.