5 comments about XML in a Nutshell, Third Edition.

1. O'Reilly's XML IN A NUTSHELL is, like all entries in the Nutshell series, a desktop quick reference. It provides concise information about nearly all matters of XML, and is split into roughly four parts. The first introduces XML, the concept of tags, well-formedness, Unicode, DTD's and schemas, namespaces, and so forth. The second provides an overview for the many formats that are built upon XML, such as XHTML, XSL:FO, Docbook, etc., and technologies that plug-in into XML, namely XSLT, XPath, XLinks, XPointers, XInclude, and CSS. The fourth covers DOM and SAX, the APIs for dealing with XML. Finally, the book ends with a "Reference section" for various technologies covered earlier in the book, structured much like O'Reilly's pocket guides. I found the Reference section somewhat inconvenient, it causes flipping back and forth when each section could have been simply integrated with the previous discussion of the relevant technology earlier in the book. Furthermore, the book ends with a long series of Unicode character tables, which are of limited utility, as they cover only a portion of Unicode, which has already expanded in the time since, and these tables simply bloat the book a little.
   
   This third edition is especially admirable for its advocation of schemas, whereas many other XHTML publications would mention only DTDs.
   
   XML IN A NUTSHELL is emphatically not a tutorial for XML, in spite of the friendly introduction to the markup language that opens the book. For each of the technologies mentioned herein, you'll want a separate book. For XPath especially, O'Reilly's XPATH AND XPOINTER is worth getting. XML IN A NUTSHELL instead provides only a quick reference for matters the reader is already acquainted with. Now, much of this quick reference information can be freely had on the Web. I'd recommend the book only to those who are fortunate enough to have someone else cover their book expenses, or can get it from their library, or those who simply adore print documentation.



2. This book claims to be your only needed guide in XML and related topics. It covers almost all you can imagine. I liked it very much and glad, that I have a book, that I can use like XML reference.
   I have just nothing to say about this book except it contains ALL information one can need on XML.



3. This book is by far the best book I've read on XML. Typical of O'Reilly "In a Nutshell" books, the converage of XML is fast paced and complete. Your money will be well spent on this book. I even think most beginners will do well with this one!



4. XML: the grab-bag, so-what-you-will, make-it-up-as-you-go-along, there-are-rules-strict-rules-(sort-of) technology that bends you to its will as much as you can bend it to yours. And this book is a decent round-up of the most common, widely-deployed implementations -- with enough general knowledge to help you sort through the more specific ones (or help you in creating your own).
   
   A better title for it might have been: "XML: A Developer's Almanac". (Which, I suppose is a good-enough alternative title for any book in the O'Reilly "Nutshell" series.)



5. The book is a reference for all XML standards ( XML , XPath , XSLT , XLink , XSL-FO , XML Schema , DTD , Xpointer , Xinclde , CSS ) and also covers DOM and SAX for manipulating XML , although the book covers the basics of XML in the first five chapters , the rest of the book assumes you have experience with the XML standards and need a complete reference for them , and the book do thr right job for that :) , it's the best reference available for XML .

5 comments about Beginning Programming For Dummies (Beginning Programming for Dummies).

1. So I finally decided to try out the "For Dummies" books and must say it's a decent enough first step. I've always had an interest in learning some programming...mostly for fun but also because it seems that a basic understanding of computer programming is becoming more and more necessary...instead of taking a course I decided to learn a little on my own to see how it goes... The book is very easy to follow and explains things pretty well. I am definitely happy with the purchase and will continue studying programming. Would highly suggest for anybody with the desire to pick up a new hobby. Just purchased Robot Building for dummies...we'll see how that one goes.



2. A good overall explanation of programming in general. Becoming proficient in any of the languages taught, I think, will require additional reading. However, the basic concepts and building blocks of programming are well laid out for the reader. A great starter for someone with no experience in programming.



3. As a Computer Science student with NO PREVIOUS knowledge of any programming language, this book has been extremely useful to grasp the basic concepts of programming.
   Recommended purchase.



4. Unfortunately I have a copy of this book published in 1999.
   There are many errors. I'm no programmer but I know you can't name the same variable 2 different ways [mynum% vs number%] and expect the program to work. Those typos -and the : instead of ; typos - I can fix. Some of the others my newbie self can't figure out.
   
   I was enjoying working my way through the book until I got to Chapter 12 where the errors were just too much to cope with!
   
   I'm guessing if you have a newer edition you'll be fine, don't buy the older editions unless you like to solve mysteries.



5. Excellent service, the book is as described. My student has been using it with great success.

2 comments about C# 3.0 Unleashed: With the .NET Framework 3.5 (Unleashed).

1. This is another well written book on C# .NET by Joe Mayo. I've been coding with the .NET framework and C# for the last couple years and consider my skills to be intermediate. C# 3.0 Unleashed is a great addition to my resource library and I reference it frequently for core and 3.5 framework functionality.
   
   I'd recommend this book for C# beginners as well as intermediate/expert level programmers. The topics and chapters are arranged in the proper order for natural progression and are easy to follow containing many solid coding samples.
   
   I look forward to continuing to learn C# .NET and its new additions with this book as my pilot.



2. Want to learn C#? This is an excellent place to start. Joe Mayo has outdone himself with a book that not only makes an excellent C# reference for veteran developers, but is also THE ideal learning tool for absolute beginners. The biggest hurdle for burgeoning developers is getting past all the new lingo, and most authors seem to blithely forget that fact. Not this one. Every time a new term pops up, it's carefully explained. Not just that "what" either, but the "why." I'm often disappointed by reference books, especially ones regarding programing languages... they're expensive while generally being both cryptic and incomplete. However, C# 3.0 Unleashed is just so logically and intuitively organized that it's a wonder every other reference book isn't laid out exactly like this one. For those looking for some LINQ help, there's several sections specifically dedicated to LINQ in it's various forms (LINQ to SQL, LINQ to SQL)... although, for completionists, ADO.NET is also covered. The only down side? It's not available on Kindle yet!
   
   Whether you're interested in learning C#, just brushing up on your programming skills, or are looking for an easy-to-read, well-organized reference - give this book a serious look!

5 comments about Agile Project Management: Creating Innovative Products (Agile Software Development Series).

1. This book is a thoroughly enjoyable read, from the emphasis on principles, the excellent job navigating the difficult territory of the line between prescribed process and anarchy, and the stages a team goes through as it embraces an agile style of development. I even thought that the hypothetical story added a nice element of repetition to each section that helped drive home the main points.
   
   The one thing I would've liked was for this book to get off the fence and decide to be software-related. Almost every example is software related (except for the basketball analogy that got beaten to death...), but it goes out of the way not to specify software practices because this is about arbitrary project management. The book's in the "Agile Software Development Series" and the author is primarily a software consultant. I'd prefer it stuck to software rather than trying to go for broader appeal because there were several practice areas where detail was elided on that basis and could've really helped make the practices more concrete.
   
   Also, it would've been nice to have a little grid mapping up common-day software development methodologies like Scrum, XP, FDD, and DSDM against the practices in the book. I tried to do it in my head, but once you get past 5x5, it's something that should've been provided.



2. As someone who has managed large custom software projects and programs for 20 years, I was concerned that applying Agile to project management would simply mean burndown charts and the like. What I found in Highsmith's book is a perceptive understanding of how people think, feel and actually work on projects. Approaches that take human behavior into account, in my experience, are far more successful than those that don't.
   
   The concepts covered here, if really absorbed and understood, can benefit any project. I found Chapter 7 to be the most valuable for my current product development team, and ordered copies of the book for all my managers.



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



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



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

5 comments about Starting Out with Java: From Control Structures through Objects (3rd Edition).

1. THIS BOOK IS NOT AVAILABLE AS DESCRIBED. The description clearly states the book is a hard cover but no hard cover is available. I tried resolving the issue with Amazon, but all they did was send ANOTHER soft cover.
   
   For $100 you should get what you were told you were going to get. Other then being VERY VERY VERY disapointed with my Amazon experience, the book reads well and is ok for the very beginner.
   
   Over all I was not impressed by the book, or by Amazon's attempt to resolve my problem.



2. This is an excellent text for students to learn Java, and Object-oriented programming. The introduction of control structures first allows the beginning programmer to master the ideas of loops / selection, before tackling the more abstract concept of objects, and classes. The examples and explanations are very gentle on the reader. The frustration level for beginners is quite low. I have taught Java programming for almost 10 years, and have used many different texts - this one works for students who have little (or no) programming experience.
   Colin Archibald, PhD



3. If you read the reviews of this text and its earlier editions, you'll see that it's nearly always praised by intro CS profs and students alike. Only this 3rd edition has gotten a real 'ding' by a reviewer, and that came more from that one individual's problem with Amazon than any real fault found in Gaddis' text itself. The guy's anger is understandable, though, as the price of this thick *paperback* book is simply absurd - as is the case with so many college textbooks these days... especially those in subject areas considered the gateway to lucrative careers. How can the publishers possibly justify their pricing? They can't... it's mostly greed. They figure CS students will just borrow a ton of money for their education and then pay off their inflated loans with their huge salaries, later!
   
   Anyway, end of rant. What I would suggest, though, is to consider using an earlier edition of Gaddis' text - used - if ninety plus bucks is too much for you. For the purpose of introductory programming in Java, very little is lost in using the first edition, "Starting Out with Java 5". As I write this in 2008, Java is 13 years old and has become a mature language; very few basic features or keywords are deprecated anymore, and all of the latest and greatest extensions are mostly beyond the introductory level of this textbook. What the first edition did well - build a firm foundation for understanding programming structures and object oriented features in basic Java - all editions still do extremely well. The second edition, and the third, however, are incremental improvements... not essential to getting one's students off on the right foot.



4. This book has pleased me a lot.I have 2 other books for Java which are waste and I never open then from the day I started reading this book.Tony Gaddis has explained every concept in detail.I am a beginner and this book is a very good choice for beginners.The examples in this book are explained so well with no errors which makes it even more good. I want to learn EJB also if his book is available.



5. i never received the book.... it is over a month ago now and i have no book and no refund.....chances are i will continue to use ebay for my textbooks, atleast they arrive on time

5 comments about Advanced ASP.NET AJAX Server Controls For .NET Framework 3.5 (Microsoft .Net Development Series).

1. This book covers literally everything you would ever need to know about using AJAX on the ASP.NET platform. It is full of useful examples. I find my self referring to it quite often.



2. This book has a lot of details. It's hard to just get on with it while reading thru the chapters because the authors seem to think they should try and combine reference material with learning material. Don't get me wrong, I like details, when I need them. However, it is really hard to just do any example in this book without getting bogged down in why rather than how. I think chapter 10 actually starts in on "How", but that's TEN chapters and 500 pages into the book!?!
   
   My other complaint is the vocabulary in this book can sometimes be a complete put off. Instead of saying things like "server side" they say "server-centric" which I guess means the same thing, but why change what everyone is used to saying?
   
   But, the book does have a lot of details and it does belong on your shelf if you want to learn serious ASP.NET AJAX and have a good reference for it. I just don't think it's the book you should read from cover to cover, especially as an intro. Dino Esposito's book is probably a better start.



3. I started programming on the internet with Internet Explorer 2.0 on a Mac Performa using notepad, and then using Claris Home Page. I was using the AJAX technologies well before 2000. It is interesting to see how engrained into our browser development they have become. A few years later I started developing Windows Form applications, which move into the Smart Client context, and now RIA using WPF and Silverlight. I have gotten my hands dirty with browser applications a few times since 2002, but I try to avoid them like the plague.
   
   I am a firm believer that the browser is being abused, would love to develop every day without it, but have found that is still not possible today when targeting home users and environments you do not control. That is not the case with our project, we should be using WPF, but those in charge do not care.
   
   Why all the useless blather? Because I want you to know I have absolutely zero interest in ASP.NET AJAX, but I have to get up to speed on it because it is being forced on our team.
   
   That said, this book sucks, because it is written so well I cannot put it down. These guys zero in on ASP.NET AJAX Server Controls, but they take the time to go in-depth on all the technologies that ASP.NET AJAX Server Controls interact with. Including JavaScript, JSON, HTTP Handlers, the ASP.NET AJAX Extensions, the ASP.NET AJAX Toolkit, REST, and WCF.
   
   This book has given me a new perspective on the present day browser environment that will make this next project enjoyable.
   
   If you are getting started with ASP.NET AJAX I highly recommend this book. It digs into the guts of ASP.NET AJAX and will give the inside story on how the ASP.NET AJAX Controls are working and how to build high quality controls yourself.
   
   I would suggest being proficient in ASP.NET, have a good understand of JavaScript, and have played around with the ASP.NET AJAX Extension and the ASP.NET AJAX Toolkit.
   
   The examples in the book are great, and the downloadable code is well organized and very usable.



4. This is an excellent book for developers looking to lean more than just the basics of ASP.NET AJAX, to truly understand how ASP.NET AJAX works. This book contains some fairly advanced subjects that are probably too much for a beginner, but great for the experienced developer.



5. This is a fine resource for ASP.NET developers who want to build high performance, data-driven Web applications with a richer user interface. The introduction of ASP.NET AJAX 2.0 extensions caught many of us off-guard. We were suddenly thrown into intensive JavaScript programming on a Microsoft platform. Faced with a major learning curve, many of us fled to the convenience of the UpdatePanel control as a stepping stone.
   
   There's no getting around it, it's going to take effort to get to the next level of AJAX capabilities using Microsoft's library. This book takes you into that journey - but not necessarily by the most direct route.
   
   The first third of the book feels more like a solid ASP.NET AJAX reference than a "how-to-do-it" tutorial. The early chapters cover the library's types, namespaces, and classes in depth. It just seemed too early and too dry to be dealing with the nitty-gritty of the platform.
   
   In my view, the book should start at Chapter Five. That's where you really make use of client-side functionality by adding it to server-based controls. As the authors point out, the AJAX library extensions help you overcome inconsistencies among browsers. You learn practical steps such as adding script resources, configuring ScriptManager, and getting into extender controls. The book leads you through the creation of an Image control extender that loops through a series of images at runtime. It's in this hands-on chapter that you really start to grasp the concepts. There's a substantial chapter of localization in ASP.NET AJAX. If you're taking on a translation, it would certainly be worth the price of the book.
   
   At the outset, I referred to the UpdatePanel. It could be called the "lazy developer's AJAX control". What I learn from Chapter 7 is that the UpdatePanel can be a real headache for control developers. The authors warn of unexpected problems when your carefully-crafted control finds itself inside a partial postback environment.
   
   The book's coverage of the asynchronous consumption of web services is solid. The authors go into all the important acronyms such as REST, and explain WCF from many angles including creating data contracts and service contracts.
   
   In the chapter on Application Services, I discovered how much I didn't know about the client-side use of ASP.NET's Membership, Role, and User Profile services. If these AJAX extensions to the server-side API's escaped you too, you'll really benefit from the chapter.
   
   Every ASP.NET developer knows about the AJAX Control Toolkit but Calderon and Rumerman take it further. They explain the overall architecture and then dig into how you can harness the Toolkit (and especially its animation support) in your own controls.
   
   In summary, this is a very good book for learning to write your own AJAX controls. My main complaint is that the cart comes before the horse... You want to dig into building something interesting (call it 'instant gratification' if you wish) but need to wade through several chapters of dry architectural and reference-type information.

5 comments about SAS Certification Prep Guide: Base Programming for SAS 9.

1. For novice and experienced programmers who wants to write certification exam its a good reference book. I recommend to buy this book.



2. The most notable attribute of the SAS Prep Guide is that it contains a lot of information not included in the two programming classes that I've taken from the SAS Institute (Base Programming I and II). The classes were great, but the book adds even more material (and if it's on the test, I want to know about it!). The book is thorough, over 750 pages of material and includes about 10 questions at the end of each chapter as a test (answers and explanations in the back of the book). Also, the book doubles as a reference guide in case you're stumped and need a resource. I have not used the CDROM at all and thus have no comments in regards to it. Overall, I suggest it, especially if you can get your company to pay for it!



3. I bought this book and read it many times before the exam. Took notes for concepts that are confusing or may be tricky(like Do while/Until, Length etc.). Passed the test (90% questions correct!) and now preparing for the advanced test. The quizes on the back are good but a bit easier than the test. I also referred the e-planetlabs study guide which had better quizes. Then I reviewd this book again to clear some concepts. Overall, SAS base test is pretty easy if you have these two reference materials. Answering 45 correct questions out of 70 is not that tough. Also SAS website has a mock test which might help practice, but i suggest the e-planet. Good luck.



4. Buying this book from Amazon saved me time and money. I was worried about the cd not being included with the book at the time of purchase. However, the book was brand new with cd wrapped in a plastic wrap. I am very pleased to order this book from Amazon.



5. This is a great book if you are preparing to take the SAS Exam. It covers everything you need to know for the exam and it is very easy to understand. I was able to pass the exam after studying with this book.

5 comments about C Programming: A Modern Approach, 2nd Edition.

1. in order to really understand what was going on you need to intently read every single word. There are no solutions for the excercises which i thought were too difficult, and many times the means to find the answer could not be found in the chapter.



2. This book was an excellent complement to the professor I had for basic C programming. I'd venture to say that even someone with little to no computer experience could learn from it. One really nice feature is the Q & A section where obvious questions about the material are asked and then answered by the author such as: "Why is the C language so terse?" There is not an excess of information, but it gives a great deal of examples and even source code so you can see how the system compiles it. If I were teaching myself the C language, this would probably be the first book I went to.



3. I ordered K.N. King's ``C Programming: A Modern Approach (Second Edition)'' from Amazon for my recent birthday. Having had more birthdays than I care to admit, this gift to myself is right up there with a Lionel train set I got for my eighth birthday (not from Amazon, of course -- it didn't exist that long ago but passengers trains sure did :)).
   
   In this second edition, I think that KNK is now the logical heir to K&R. That's not meant as blasphemy -- Kernighan and Ritchie's still great volume is around 20 years of age and it's unlikely they'll be getting together for K&R3. The C language has undergone enough changes (with the amendment of 1994) and C99, that a ``Modern Approach'' really is needed.
   
   There's another author familiar to readers of the comp.lang.c newsgroup for his approachable, engaging writing style. That author is a wonderful writer but doesn't let the truth get in the way of good narrative. King, though, is an equally engaging writer but is obviously passionate about correctness and adhering to the C standard. He's also meticulous about portability so that the examples are written in pure C and not some platform-specific variant.
   
   I've the entire book and can find hardly anything even nitpick. Aside from a minor style difference about using parentheses with the ``sizeof'' operator, which King explains his rationale for doing so, that's about it.
   
   His explanation of C99 (and the differences from C90 are clearly indicated) made me aware of some really nice features of the current standard for the language (and makes me wonder why one very notable compiler implementer hasn't yet supported C99).
   
   In short, get this book. The Q&A sections at the end of each chapter are very well done. The exercises and programming projects help to amplify the material presented. And King's examples will teach you more about barcodes and ISBN numbers than you ever thought possible.
   
   If you can appreciate the work of a fine craftsman in film such as Martin Scorsese, you'll find that King is of that caliber in the realm of lucidly dealing with this technical subject.



4. I am backtracking a bit by taking C Programming. I already know C++ and C#, but C Programming is required for my major. This book is easy to understand, or maybe it is for me with my previous experience. However, it seems that the non-programmers in my class are grasping the concepts using this book. The only down side is that the book has errors that were not caught in the editing process prior to publication. However, the author maintains a website that identifies the post publishing errors and also contains solutions to select problems from the book. I like this book. It is concise and light, so it does not weigh down my backpack.



5. I received my book in pristine condition and the seller had very fast and courteous service. I would definitely consider purchasing from this seller again! :)

5 comments about Learning PHP & MySQL: Step-by-Step Guide to Creating Database-Driven Web Sites.

1. It is not quite clear to me how any technical editor, let alone from a publisher specializing in technology books, could pass this text as is. It is quite obvious that the authors may know their way around developing simple database-driven web sites but completely miss basic programming topics (OOP, constructors, static variables etc. - all are explained in confusing and, at times, incorrect language).
   
   Add to that grammatical errors, and perhaps a reminder that "kraut" is a derogatory term better left out of a mainstream publication, and it's quite baffling how this book made it to print in its current form.
   
   I haven't seen other publications on the topic to compare against but this one certainly was a disappointment.



2. While this is a typical O'Reilly book (marvelously and expertly written), there weren't many examples of utilizing what you just learned such that it would sink in. It also pre-supposed a bit (not much mind you) of programming experience/knowledge of which I have none. The description is a bit mis-leading that way as it states that if you know HTML and are ready for the next step this is the book. It should say, if you know HTML, a bit of C, or PERL, and some SQL you will benefit from learning PHP & MySQL. Not disappointed, just not the book for me...



3. I have not bought a textbook in over five years. Back then, O'Reilly was a reputable brand. So when I needed to learn PHP and MySQL, I bought this book without doing any research. I will never blindly buy an O'Reilly book again.
   
   I got to page 11 before finding my first typo. After that, I lost track of all the typos and coding mistakes I've seen. Mind you, this is the 2nd edition of this book. Clearly, the authors did not proofread their book, nor did anyone else at O'Reilly, nor did anyone who read the 1st edition (?). I have learned to not trust anything in this book and instead use google for my php/mysql questions. Also, the mistakes are not all obvious typos -- some are mistakes in reasoning, which I can catch because I have extensive experience with computers.



4. Maybe a genius or someone who already understands PHP basics will benefit from this book. I have made great progress with a number of instructional books, but got stuck in Chapter three of this one. It seems that important terms and concepts are not explained, not explained well, or explained in pages after the terms and concepts are first used.
   I'm going to search for another book on PHP & MySQL.



5. This dreadful book is so far below O'Reilly's normal high standard that it's hard to believe anyone at the company saw it before publication. It is riddled from start to finish with typos, technical errors, bad coding practices, contradictions and statements that are just plain wrong. It's quite baffling that O'Reilly would let a book this bad hit the shelves.
   
   What is particularly worrying is that this is the second edition. The first was also full of mistakes (see the reviews on the O'Reilly website) and the publisher seems to have acknowledged this by rushing out this second edition only a year after the first, but the new edition fixes few of the problems of the first while introducing a host of new ones. One of the worst books ever published by O'Reilly. Avoid at all costs.

5 comments about Design Patterns in Ruby (Addison-Wesley Professional Ruby Series).

1. I am a Java developer whose Ruby experience is limited to firing up the interactive Ruby shell for a Hello World, or reading the first chapters of Programming Ruby before drifting away and vowing to learn Ruby "when I have more time". I work with the author, and purchased this book solely on the strength of his training courses and lectures. Russ Olsen in book-format is just as effective a teacher as he is in person.
   
   The book is a hybrid reference/Ruby-introduction book which provides the best of both worlds -- I was able to read it cover-to-cover without losing interest, something I could never quite accomplish with the original GoF Design Patterns text. Each chapter also functions as a modular unit, with concise introductions and conclusions that will be great on a day when I pull it off my shelf for use as a reference book. The Design Patterns provide a nice playpen for the sections on Ruby coding practices and features, and the coding sections give a better context for the Patterns.
   
   Each Pattern is discussed in theory and in real-world code, and the author is very clear about the benefits and pitfalls of employing them. In addition, the book provides a solid, likable profile of the Ruby language without the evangelizing common in other books. Code examples are concise and useful, and the writing style is humorously engaging without falling into the trap where engineers-turned-authors suddenly believe they are stand-up comedians and sprinkle every paragraph with a multitude of grating jokes. There were a few mistakes in the text, but all of them were already captured and corrected on the book's web site.
   
   In my library of tech books, the best books, the ones I constantly revisit, are not the ones that show me how to do something -- they are the ones that place what I do in a wider context and show me the possibilities of what CAN be done. Although I do not currently use Ruby in my day-to-day work, I can see this book becoming invaluable when that day comes.



2. By far the most accessible design book I have read. The author not only explains the pattern and the reasons for its use, he then goes on to show a traditional implementation of the pattern followed by a Ruby-specific implementation. By far the best design patterns book I have read yet.



3. I never really understood the need for Design Patterns. After reading several blogs, and listening to other programmers, I thought that Design Patterns might even somehow be harmful to my programming education. I felt that just by learning what they were, I'd somehow pollute my thinking to the point where I wouldn't be able to program without seeing a pattern in there somewhere. When I heard of the book Design Patterns in Ruby, I flinched. What good could possibly come from introducing Design Patterns into Ruby, I asked myself? Fortunately, my initial prejudices were unfounded. Design Patterns in Ruby is not some secret plot to turn all of the Ruby programmers into mindless drones; it is a very thorough introduction to Ruby, Design Patterns, and Object Oriented Programming concepts. Design Patterns in Ruby helped me to finally look critically at Design Patterns, and see them as something not to be feared, but as something that could be useful, even in my Ruby programming.
   
   Design Patterns in Ruby is written with the idea that while the reader might be a good programmer, they may have somehow missed what Design Patterns are, or the reader might not know much about Ruby. The first two chapters rectify this by introducing the reader to what exactly these Design Patterns are. The author explains precisely which of the 14 of the original 23 "Gang of Four" patterns are covered in the book, and reasons why the 14 patterns were chosen. Chapter 2 is a quick introduction to Ruby, just to ensure everyone is on the same page. The author, in a single chapter, clearly explained concepts that other books I have read couldn't clearly convey, even after several chapters. Any doubts that I had of the author's abilities in explaining Design Patterns in a way that I would understand were completely gone by these chapters.
   
   The actual Design Patterns in Design Patterns in Ruby have a similar format throughout the rest of the book. First, a small anecdote begins the chapter, explaining either a real-life situation where the patterns would be handy, or tying the pattern to one of the other patterns in the book. The meat of the chapter describes how one would implement the pattern, usually starting with a direct port from another language like C++ or Java, and gradually working it into something more Ruby-like by the end of the section. After the pattern is worked into a more Ruby-like format, the author then describes how to really abuse the pattern. Lastly, the author points out where this pattern is used in the Ruby, Rails, or other Ruby code, followed by a quick summary. This format works quite well, especially for programmers just starting in both Ruby and Design Patterns, while advanced programmers will learn better and more effective ways for implementing (or abusing) the patterns. Providing where the pattern is used in the code is also an excellent learning tool for the reader, and gives a baseline for the reader on where to look for more examples. The format also makes the book engaging. I found myself wanting to read the book, which is an experience I can't say I shared with the original Gang of Four Design Patterns book.
   
   In addition to 14 of the Gang of Four patterns, the author talks about three Ruby-specific patterns. The first is the Domain Specific Language (DSL) pattern. Rather than defaulting to discussing Active Record (arguably the most famous DSL in Ruby), the author actually creates a DSL called "PackRat" which is a language for managing backups. The second pattern is Metaprogramming, which is ubiquitous in Ruby. The last pattern in the book is Configuration Over Configuration, the mantra of Rails. Each of these patterns compliments the other patterns in the book, and add to the original patterns discussed earlier in the book.
   Design Patterns in Ruby is an exceptional book. It distills the best of the "Gang of Four" patterns that are of significance to Ruby Programmers, while adding several patterns that show up throughout Ruby and Ruby on Rails code. The author's style and the book's format make for an easy and informative reading experience. I can heartily recommend this book for all Ruby developers, both beginners and experts, and can especially recommend this book for those like myself who didn't think the original Design Patterns was anything to give attention. Design Patterns in Ruby has earned a permanent place on my shelf.



4. This is a marvelous book, ideal if you're an experienced object-oriented programmer who wants to learn to use Ruby with the idioms particular to it, and not remain frozen in the techniques of traditional, statically typed object-oriented languages. Ruby is a dynamically typed language with many unique features, and this book was invaluable in my learning to use it as such. There are 16 design patterns covered, 3 of which are particular to the Ruby development environment. With each pattern is presented first the traditional approach using Ruby as a straightforward OO language, followed by the Ruby approach which takes advantage of the idioms and techniques particular to the Ruby language. With each pattern is introduced a new Ruby idiom, making the book a tutorial in advanced Ruby programming techniques.



5. If you're already a programmer, this book an excellent way to learn Ruby. It shows how to apply a variety of common and largely language-independent programming structures ("design patterns") in "the Ruby way". Along the way, you get a great introduction to what makes Ruby unique, and the idioms commonly used in the Ruby community. I especially liked that the author often showed multiple implementations of each pattern, each implementation being more elegant and Ruby-esque than the last, and included a discussion of when each might (and might not!) be appropriate. I also appreciated the helpful discussion of the ways you might shoot yourself in the foot with each pattern in Ruby, as well as the pointers to where you could find the pattern used in Ruby "in the wild" (in various software freely available on the Internet).