3 comments about Developing More-Secure Microsoft® ASP.NET 2.0 Applications (Pro Developer).

1. This is a book by a MS Developer Security MVP for any and all developers writing ASP.NET 2.0 applications. Not only does it cover all the usual suspects and provides practical prescriptive guidance on how to deal with them with examples; it also deals with the tough "hot topics" like partial trust. The book is both complete in breadth and depth and really does provide a single good reference book on ASP.NET security.
   
   I can not recomend it with more guster.
   
   Confession I helped write the tools chapter which is why I know (and yes I am a fellow MS Developer Security MVP)!



2. I really wish I could give this book 6 stars, it has been an indespensable resource for learning techniques to develop more secure applications. With so many dangers lurking out there it is increasingly important to not only be able to develop secure applications but to understand the .net security mechanisms as well. This book will leave no questions unanswered, if for no other reason purchase this book for chapter 8 on partial trust, I have not come across any resource that covered this topic so thoroughly. It's treatment of sandboxing and code partitioning alone make the book worth every penny paid. If your looking to continually improve the quality of your code and sites don't leave this book off your list.



3. I am an ASP.NET newbie and found this book very helpful in understanding authentication, authorization, role based security, input validation etc. I am a desktop developer and found the web development model difficult to understand initially but this book cleared up my mind in the security related parts. The book is written in a very clear and concise manner and uses diagrams to explain concepts which which I found very helpful. There are practical advices sprinkled all over the book along with the "why" of it.
   In short, this is a very well written book which improved my asp.net knowledge and skills considerably. Highly recommended.

5 comments about Database Administration: The Complete Guide to Practices and Procedures.

1. This is a well-written, well-organized guide to the practice of data base administration. Unlike other books on general database theory or relational database theory, this book focuses more directly on the theory and reality of database administration as practiced by database professionals today, and does so without catering too much to any specific product implementation. As such, Database Administration is very well suited to anyone interested in surveying the job of a DBA or those in similar but more specific roles such as data modeler or database performance analyst.

   Yet, even with that direct focus on database administration, the author succeeds in covering a great deal of ground and cutting a rather wide swathe across the database spectrum, doing so with rigor and expertise and the benefit of experience. While the book will not and is not intended to serve as a reference substitute for product documentation, it will nonetheless enhance your knowledge, and I find it of such quality and utility that I recommend it to anyone in the database field in general. Consider it a base text to serve alongside Date and Codd.

   Among the nice touches, the author includes discussion of database denormalization, often missing in discussions on database design. Chapters end with both a set of review questions and a Suggested Reading section, and I find myself in agreement with most of the suggestions. An excellent Bibliography section follows the text. I would have liked to see some discussion of the difference between relational domains in theory and their implementation in practice, particularly as it impacts the design of integrity constraints. Even so, Database Administration is an excellent book and I highly recommend it.

   - Sal Ricciardi




2. I've forgotten how many times I've recommended this book to people. It's well written, to the point, and covers the topics that you need to know to become an effective DBA.
   
   - Scott Ambler
   Thought Leader, Agile Data Method



3. This was a good introductory book about all the different
   terms and concepts in generic database administration.
   
   This book does more to cover from the managers perspective of all the
   extra stuff that managers would think about in terms of data
   loss, disaster recovery, recovery, etc.



4. Database Administration: The Complete Guide to Practices and Procedures was delivered sucessfully. I enjoy the book.



5. I bought this book as a required text for a class I was taking. While I find text books dry and difficult in many cases, this one was different. Mullen writes with some well placed humor, and yet covers a very large spectrum of information.
   
   This is not light reading, and it goes into quite a bit of depth on the various topics that a DBA needs to know, like backup and recovery or indexing. He doesn't get into how you mechanically do the procedure on each DBMS, but rather, he goes for an under the hood approach, so that you understand how/why the DBMS works. After each chapter he gives very good references for additional reading on each topic.
   
   Even though Mullen is a DB2 guy, this is not a DB2 book, it is well rounded non-platform specific. While some books can be TOO generic and not useful, the author treads a delicate balance and delivers value in every chapter of the book.
   
   One final note, he does convert real life experience into this text and I really appreciated the information he provided on denormalization and some other aspects that are not covered by other books.

5 comments about Beginning Active Server Pages 3.0 (Programmer to Programmer).

1. This text is so packed with information, it even goes beyond asp and introduces XML and COM+....so well written, so concise, publishers throughtout the country need to learn from wrox' writers on how to do technical books right! Every bit of code is explained in great detail, and while there are some errors, the website covers nearly all of them. Case in point: I won't be selling my copy back!



2. This book starts by giving an overview of how the browser, server, and pages interact to deliver web-based data and pages. The first 3 chapters, and the XML intro, are worth the cost of this book. I started this book with very little understanding of how dynamic web pages are delivered over the net, and am now ready and anxious to take on my first web development challenge. Can't wait to put the info in this book to use! The writing style is great also - very seamless and easy understand, even after 6 authors compile their knowledge into one volume!!!



3. Prior to purchasing this book I had no experience with ASP whatsoever. One day at work I was told that I needed to study up on ASP, and fast. I didn't really know where to start, but I ended up with this book, and it has been a lifesaver. I took the time to work through the examples in a select few key chapters, and was amazed that after only a couple of days I had developed the skills necessary for basic ASP development.
   
   Now its been a few months, and the book still serves as a useful reference. It is extremely well organized. The examples are basic, but definitely teach the fundamentals needed to become a competent ASP developer. It will not make you an expert, but that's not its purpose anyway. It excels at relating the relevant information in an understandable and easy to learn format. For me to be developing with ASP in only 2 or 3 days is a testament to the quality of this book. I've never read a Wrox book before now, but I will definitely only purchase Wrox books in the future.



4. Beginning Active Server Pages is an all encompassing book on classic ASP web server development. The authors explain in great detail from the beginning on how dynamic web development works. No matter what technology you use (PHP, Coldfusion, JSP), how a web browser requests a page, the web server send the request to the server-side engine and/or does a database request and send the result to the browser. The book assumes no previous knowledge of web development and explains the basics very well so that any reader can start from any skill level.
   
   The beginning of the book discusses what software you will need to get started which basically is either IIS (Internet Information Serve) or PWS (Personal web Server) in a Windows environment. How to install, test and configure the web server is discussed as well as setting up user permissions and virtual directories. This is a great starter to making sure the reader has all the information to get started on creating their first ASP web page.
   
   The author continues explaining basic scripting techniques and language syntax of web scripting (VBScript) and explaining the differences between client and server side scripting and how the IIS engine interprets the request. Also covered early are the intrinsic ASP objects such as Request, Response, Server objects. A good review of some of the basic components of this very robust development technology.
   
   The book then goes into send and receiving data from web forms in showing the reader some very useful but basic examples to get you started. The book covers in the next few chapters (4 - 5), in detail the basics of VBScript language such as variables, operators, strings, arrays, control statements (if, case, loops) and functions. The next chapter (6), goes into the concept of objects, methods, properties and events which explain to the user that almost everything is an object in ASP and the importance of this fact as well. Some OOP concepts such as encapsulation, inheritance, and polymorphism are reviewed with some nice examples.
   
   The next two chapters cover many important ASP objects in great detail such as Response, Request, Application, Session, and Cookies. These chapters cover most of the most used objects that will be used in almost any ASP application. When you can master these objects you will have a great understanding of the fundamentals of ASP applications. The authors do a great job of explaining these important topics to the reader that it gives you more motivation to read more and learn more. Unlike other books that try to explain too much and confuse the reader, this book explains just enough in English other than techo-bable.
   
   The rest of the book covers all types of database access using connects, recordsets, cursors, ADO, locking, filtering data, SQL syntax, and much more. Among other topics covered at the end of the book are focusing on advanced topics such as XML, Transactions and COM+.
   
   The book is really all you need to learn and master ASP to develop dynamic web applications for yourself.



5. Like the others have said... this is a good starter book for those looking to learn the older ASP technologies, since you may need to know a little of this if you are messing with older sites. I would recommend this book. However, the one thing that is wrong with this book is the MASSIVE amount of grammatical errors and typing errors.
   
   Its calling out the wrong variables in certain situanions and mislabeling methods and procedures. Once you are aware this is happening in the book you just need to be mindful and know you aren't crazy, its a typing error. I hope Wrox has started taking their textbooks to the editor and getting them proofread, because it's a shame a book this good is peppered with so many errors.
   
   In closing, this is worth the read and it will surely help you on you way to learning ASP 3.0.

5 comments about Service-Oriented Architecture (SOA) Compass: Business Value, Planning, and Enterprise Roadmap (The developerWorks Series).

1. The whole subject of SOA, or Service Oriented Architecture, is getting to be ever-more mainstream in IT organizations. Being able to build systems using a web services architecture presents some very real advantages, but how do you know where to begin? From an architecture and structure viewpoint, this book does a pretty good job... Service-Oriented Architecture Compass: Business Value, Planning, and Enterprise Roadmap by Norbert Bieberstein, Sanjay Bose, Marc Fiammante, Keith Jones, and Rawn Shah.
   
   Contents: Introducing SOA; Explaining the Business Value of SOA; Architecture Elements; SOA Project Planning Aspects; Aspects of Analysis and Design; Enterprise Solution Assets; Determining Non-Functional Requirements; Securing the SOA Environment; Managing the SOA Environment; Case Studies in SOA Deployment; Navigating Forward; Glossary; Index
   
   Given the right audience, this has a lot of valuable information. If you're a developer looking for information on how to code a web service, then you'll likely be highly disappointed. This book is *not* a coding tutorial, nor does it profess to be. It really serves as a guide on how an SOA environment can be built and leveraged within an organization. I would see this as being a great book for an application architect trying to position an organization's overall application strategy. For a person like that, all the important concepts are to be found here. There's the "why"... why be concerned with SOA? There's the "who"... Who in your organization plays a part in designing and building these services to be used by the business? And of course, there's a lot of "what"... What are the parts that make up an SOA implementation, and what does an organization have to take into account to make it all work together? It's easy enough to build a web service to look up a name or something, and to think you're now leveraging SOA. The reality is much deeper and more fundamental than just rolling out a web service here and there... An additional feature of the book that makes it unique is that it references online developerWorks articles on the IBM web site in order to add more information to the mix. Oh, and I probably should mention that since it's an IBM Press book, there's a heavy slant towards IBM examples and software. But overall, the core information is vendor-neutral, and it's material you'll need to understand in order to make an SOA implementation a success.
   
   Don't think you'll sit down, read the book in a couple of hours, and then be all-knowing when it comes to SOA. The material takes time to read and understand. But once you make it all the way through, you should be well-grounded in the fundamentals behind it all.



2. I enjoyed the book. It was well-written in clear language, presenting a concise set of principles for a successful SOA strategy.
   
   This book was an eye-opener for me. It presents SOA as something that you grow into. It described SOA in terms of the business benefits that it leads to, namely agility and flexibility. The authors filled the book with wise advice. It opened my eyes to the path that lay ahead of me.
   
   The authors suggest a close working relationship between business process owners and the technical staff. They claim this is a critical foundation for being able to create services which are indeed flexible and lead to business agility.
   
   The 2 case studies at the end of the book could have included more details.
   
   If you're looking ahead for your own SOA development efforts, definitely pick up this book as you plan projects, evaluate staffing needs, design your architecture, and consider
   software purchases.



3. This new book from IBM Press released in October 2005 provides valuable inputs for someone looking for an authentic source to obtain a roadmap on SOA. Having said that, the 11 chapters present only a high level view of the topics. For instance, it clarifies that SOA is Platform, Protocol and Programming language independent. These and other aspects relating to backward and forward compatibility, the Enterprise Service Bus, the On Demand Operating Environment (ODOE) are all compressed into one chapter, Chapter-3 titled "Architecture Elements". Chapter-4 presents the SOA Adoption Roadmap with a brief set of tips for success which make interesting reading. Chapter-4 also takes a look at existing roles in IS projects and redefines some of them and introduces new ones. The UDDI Designer, UDDI Administrator and the Services Governor are new roles that I found interesting. Chapter-5 deals with Analysis and Design of Service layers through abstraction and how to categorize them. Chapter-6 carries the interesting analysis and design discussion forward and states that finding the correct asset to solve the enterprise architechture problem is difficult. The chapter discusses 2 scenarios with pros and cons and consequences of each approach with diagrams that are good.
   
   I found these 4 chapters (3-6) of the 11 the highlights of the book. I am looking forward to delving deeper into SOA architecture from other books. This book provided a good foundation for understanding SOA.



4. I enjoyed this book and found a lot of valuable information and insight into SOA concepts and issues.



5. I read this book after reading Enterprise SOA: Service-Oriented Architecture Best Practices By Dirk Krafzig; Karl Banke; Dirk Slama. That is the best book on SOA in my opinion. So may be I am a little biased, but following are my comments:
   1. I found it highly theoretical. It tries to explain a lot of concepts, but does not use practical examples. This is in total contrast to the book I mentioned, which keeps the information interesting and readers can relate to it easily.
   2. The case studies sections seem to be done hastily and there is no practical knowledge which you can get from them. They seem to be simple applications of web services. The authors use buzzwords like hub centric architecture etc. to make them look different.
   3. Authors use all available opportunities to promote IBM products.

5 comments about Advanced .NET Remoting, Second Edition.

1. I hate it when I pay good money for a poorly written book. So when I buy a book like this and it turns out so well, I am thrilled!
   
   I have been in ".NET land" since 2001 when .NET beta 2 came out. I have written ASP.NET and Winform applications. During that time I just have not had the need to use .NET remoting, until now. The first 2 or 3 chapters are a great introduction for experienced .NET developers. I like the fact that I did not have to wade through a lot of stuff for beginners. From there the topics get advanced, with plenty of good example code to highlight the topics. Even though I had never really touched .NET remoting (except SOAP Web Services), the explanations and examples work well for me. The author keeps the examples simple, and on-topic. In my opinion, this helps to highlight the topics at hand. The content is geared towards real programmers who will be using the technology.
   
   I also have really enjoyed the authors' candor concerning the weaknesses of .NET remoting. They have already highlighted a bad approach that I was considering.
   
   I am more than happy to give this book a 5 star review!



2. This book almost contain every detail of .NET Remoting.I am sure you can well understanding the .NET Remoting with the help of this book.It gives many good tips and useful cases ,also have some additional experiences of the author.However, I am sory that this book don't have any real and integrated distributed business solutions based on .NET Remoting(I think so ,at least ), although it contains many good cases. but I still strongly recommend you to buy this book, if you want to know .NET Remoting deeply.



3. This is actually a good book, however, it approaches the subject with an extremely hypothetical view. Lack of real world examples has made reading this book a real bore.
   
   The book on the other hand offers in-depth information regarding the "behind the scenes" work of .NET remoting.
   
   Final verdict: Good value for money, but do not expect any code to work.



4. I'm never one to buy books one technology, mainly because they change frequently and you can always find tutorials online. This book however, is well written, descriptive and a must for anyone working with .NET remoting. Excellent!



5. Excellent book. Exactly what I was looking for. With it you can gain a very well understanding of the subject. simple examples that you can easyly adapt to your specific needs.

5 comments about My Job Went to India: 52 Ways to Save Your Job (Pragmatic Programmers).

1. I love this book. It's full of great ideas on how to be a creative employee who significantly contributes to her organization. I really wish I'd had it 20 years ago when starting out. Note: The title is misleading; it's not about outsourcing so much as making yourself highly valuable. Highly recommended.
   
   More at: A few highlights from "My job went to India"
   http://ideamatt.blogspot.com/2007/02/few-highlights-from-my-job-went-to.html



2. This book has a bunch of generic advice along the lines of keep up with things and don't put all your eggs in one basket. Not exactly a revelation here.
   If you read the relevant blogs, web sites and talk to people in the industry you don't need this book.



3. "Pragmatic Bookshelf" has a solid reputation for publishing great books and this book is no exception. This one ranks right up there with books like "The Pragmatic Programmer" and "Code Complete". With small bite sized chapters with specific and pointed advice, you won't go wrong buying this book.
   
   In the era of globalization -- specifically with regard to software development, the book offers a complete list of techniques and approaches to not just survive but excel in the programming world. Having lived in India for a short while, he has some really astute observations about India including some great tips related to recruiting good programmers. There are a couple of chapters available for free off the publishers website. Read them and also take a look at the table of contents. Just the table of contents is probably worth the price of the book.
   
   It is unfortunate that the title "My job went to India ..." was chosen. Apparently, the author's propensity for cuteness overcame his wisdom. Looking at the cover makes it seem like some kind of a trashy joke book and it's possible that a lot of folks might have given it the go-by judging the book by its cover. The publishers might be doing the general public a great service by releasing a new edition with some updates and renaming it while not wearing their funny hats -- maybe something like "The Relevant Programmer".



4. This book has changed the way I look at my business. There is not much to say about this book. It is short enough to read it in one weekend a I would strongly advise you to do so.



5. As a North American software developer, I definitely got a lot out of this book. I don't really fear my job being outsourced to India but I wanted to understand what the issues were with outsourcing and can IT shops in India deliver the same value at North American ones.
   Outsourcing to India is just a part of this book and the general theme is how to stay more relevant to your organization when technology is constantly changing. There is a lot of useful advice about how to make yourself more valuable to your organization (and deliver more value to your organization).
   [...]

5 comments about Data Structures and Algorithm Analysis in Java (2nd Edition).

1. Well, I have to admit I did not expect much from this book. But to my overly pleasant surprise, I found this volume quite useful both as a resource for algorhythms and data processing...Forget the Bible, this is the only book one truly needs. And it's fun to say "Java." Amen.



2. All of the practical algorithms are left as un-answered exercises! Great in depth discussion of introductory algorithms, but very few examples, mostly pseudo-code.

   INFURIATING FOR INDEPENDENT STUDY, but good if you have a professor to explain everything as you go.




3. If you don't know Java, don't expect to be able to learn the things you need to for a class. If you learned how to do alorgithms in mathematics, it may not be enough for computer science. You probably want to get a supplemental or two if you have to get this book for class. It is quite advanced and a hard read.



4. It is a nice book but i expected something better. I don't know what it is but something is missing here. I like the C/C++ version of this book better for some serious learning. On the other hand this is a good opportunity to learn java programming at the same time if you haven't mastered it yet.



5. I felt the author has a firm understanding of the concepts and truly what he wanted to convey, but this book lacked a great deal for beginners or newcomers to Java. Far too many of the examples were tough to understand and in many cases simply un-answered. This is not a book for beginners.

No comments about Software Testing Practice: Test Management: A Study Guide for the Certified Tester Exam ISTQB Advanced Level.

5 comments about A Practical Guide to Information Systems Strategic Planning, Second Edition.

1. My graduate IS/IT Strategic Planning course did not assign a text book on writing up an IS/IT Strategic Plan, so I had to track one down on my own. After reviewing at least a dozen books, I found Cassidy's to be the most practical with multiple and varied examples of the critical ideas, sections & components found within an IS Strategic Plan. There are many great examples of Mission and Vission statements and detailed sections on ROI analysis, executive summaries and the entire planning process, etc. The graphics & exhibits are easily understood and well organized, as is the entire book. In fact, other students actually purchased this book during the semester at my recommendation and our professor is looking to add this book as required reading for the course! It is especially good for those who have little to no experience putting together an entire IS plan from ground zero. Thorough, to the point, terrific examples and extremely well organized is how I would sum up this book. It will serve both students and IS/IT professionals extremely well.



2. I work for a large East Coast Utilities company. Our project team was charged with producing an "Information Systems Strategic Plan". A daunting task given multiple platforms, architectures, and technologies. Our team was experienced and knowledgeable, but lacked process direction.

   We turned to Anita Cassidy's book and found it amazingly helpful. We found ourselves referring to it many times during the planning and implementation stages of the project.

   Her book provides an authoritative reference which allowed us to cut total project time by 25%. We didn't need to argue about process, methodology, or research strategy. We went with Cassidy's suggestions and we were more than pleased with the results.

   Cassidy's simple, straightforward approach is easy to follow, meaningful, and very applicable. If you have the task of assembling an IS Strategic Plan, then this book will give you the step-by-step methodology to do so.

   Nice job Anita!




3. Half of the book deals with strategic planning which is quite helpful. Half the book deals with how to acquire an application which is not.



4. This book, like all of Ms. Cassidy's work, is straightforward, to the point and reads like a blueprint for success. In particular, she frames the objectives (Where are we? Where do we need to be? What's the best way to get there?), then gives guidance on answering the questions and a realistic and actionable plan for meeting the objectives.

   Her approach is focused on business needs and linked to the overriding imperatives and strategies of that domain. She begins by discussing the business drivers and why strategic planning is necessary, then provides a phased approach to the strategic planning process itself. This approach captures the business and technical "as-is" and "to-be" pictures, performs a gap analysis, and a plan for going from "as-is" to "to-be". On the surface this appears to be common sense, but the devil is in the details, and she provides the details. That is what makes this book so valuable. More importantly, it's obvious that she has extensive experience in strategic planning because all of the subtle issues are addressed, and her advice is on the mark every step of the way.

   Of course, one of the big issues in strategic planning is the question of what capital investments to make in software, either as an upgrade or entire replacement of company-critical systems, that align to the slected strategy. This book shows how to select the best fit to meet strategic plans, and how to capture the true costs and support requirements as a matter of due diligence.

   This book is, in my opinion, one of the better ones on the topic, and is only exceeded by her most recent book titled "A Practical Guide to Planning for E-Business Success: How to E-enable Your Enterprise". That book contains substantially the same approach as this one, but is aligned to e-business. Regardless of which book you choose, you'll find Ms. Cassidy's approach to reflect best practices, and the advice interspersed throughout the book to be invaluable.




5. I have not worked completely through this book, but have found it to be very readible with sound information. Everything does not apply to my situation (very small organization), but the concepts are clear.

5 comments about Chris Crawford on Interactive Storytelling (New Riders Games).

1. This book opened up a whole new pattern of thinking for me. The information Mr. Crawford conveys in this publication is invaluable to any writer seeking to break into new areas-particularly gaming and other applications utilizing interactive storytelling. Writing for this genre requires a whole different mindset from traditional genres and Mr. Crawford succeeds at moving the reader towards that mindset.

   Time and again I see in game reviews how a particular game has "awesome graphics and great gameplay but the story and dialogue" were severely lacking. With Mr. Crawford's extensive experience in the gaming industry, he very capable gives aspiring writers every tool he or she will need to get a very good start in the industry. Throughtout the book, he stresses how important it is for the "artsie" thinkers (the writers & artists) to work together with the "techie" thinkers (the programmers) and I think this is a valuable lesson that many current game producers have yet to learn. Mr. Crawford reminds the entire programming industry that one sector of development cannot succeed without the other. He more than adequately investigates and chronicles how the different development teams can work together and bridge the "communication" gap between the "artsies" and the "techies."

   This book, while not exactly a tutorial piece, offers many examples and exercises to move the writer along in thinking like an interactive storyteller. The only real drawback may be the detail Mr. Crawford goes into. While I personally don't have a problem with this, I work with several young people who, while they are very keen on gaming development, probably wouldn't spend an adequate amount of time studying the information contained in the book unless it were required reading in a course.

   Personally I feel that any writer who wants to pursue and develop stories for interactive programming should study this book. It's not enough to read it through once, twice or even three times. This is a book which needs to be worked through section by section, until writing for this relatively new genre becomes second nature. This book will have a permanent home in my library; it is very rich in information-hats off to Mr. Crawford for producing a very timely manual.
   -Adaera-




2. In this book, Chris Crawford presents his teachings, thoughts and feelings on Interactive Storytelling, the topic that he has courageously committed the last thirteen years of his life to researching, understanding and developing.
   
   This book struck many chords with me and opened up many avenues of thought, presenting me with inspirational ideas that kept me thinking about Interactive Storytelling for the many months that followed. I own a reasonable collection of books on game development and related academic topics, and I believe this to be the single most important book in my collection. Many of the ideas within are worth the price tag alone.
   
   I whole-heartedly recommend this book to anybody even remotely interested in Interactive Storytelling, and especially designers and developers within the games industry. It simply deserves to be read.



3. In the spirit of full and open disclosure, I have known Chris Crawford for over twenty years. We are close friends and colleagues. So instead of providing a review, I'd like to comment on some of the things brought up in the other reviews.
   
   In two reviews, it is indicated that the book is not tutorial and doesn't provide specific examples. These are absolutely correct. "Chris Crawford on Interactive Storytelling" is a distillation and documentation of all that Chris has learned and created on interactive storytelling over the last thirteen plus year. He explores areas where none have gone before and he also explores areas where others have been adding insights that are new. There is definitely material here you won't find in any previously written book. However, this is a not a document of a completed journey. A couple of simple stories have been built-as proof of concept for the early working versions of the Erasmatron-but they mostly demonstrated the need for better tools. Interactive storytelling requires a new set of skills and tools. This book is heavy on theory and process, but light on examples because the theory and processes must precede the examples-and we're just getting a handle on the theory and processes. Expect to see examples in Chris' next book, which I expect he'll write once the Erasmatron is out the door and pumping out interactive stories. (I'm guessing here, Chris has never mentioned doing another book, but there will definitely be a need for a book on Erasmatron storybuilding and who better to write it than Chris Crawford and/or Laura Mixon?)
   
   William Ogles comments on Chris' writing style, which is decidedly conversational. His writing style, combined with his strong convictions, often polarizes readers and the attacks against him can be as vicious as the praise is glowing. Chris was a teacher early in his career and lessons learned from those early days drive much of his writing and speaking style. He will present gray area subjects in stark black and white and he writes provocatively. This is his method for making a point and generating thought and discussion.
   
   Indeed, it was his recent article about Women and Gaming in "the Escapist" (an on-line magazine) that provoked the single negative review of this book. The best clue to this is that the reviewer is complaining about Chris' views on women and gaming, yet that subject isn't covered in this book. Also the quotes are from his article, not from the book. Chris' point was that sales of romance novels (especially of the "bodice rippers" genre) and soap opera show that women were the primary customers and that they were immensely popular and that games that appeals to the same needs would be more successful with women than "Doom" clones. It appears to me this is rather obvious-the trick, of course, is figuring out what such games might be. The reviewer's characterization of the above as "blatant gender stereotyping" is a hard trail to follow and suggests that Chris triggered a hot button for the reviewer.
   
   Also, unlike Chris' other book "Chris Crawford on Game Design", this book is not for aspiring "game" designers-it's for aspiring "interactive storytelling" designers (of all ages) or for game designers that want to move into an entirely new and exciting field.



4. Crawford's take on Interactive Storytelling, that is the maturation of a medium which will become the dominant form on art and entertainment in the 21st century, provides a foundation upon which future efforts will either be based off of or at least reference in intellectual homage. The breakdown of the modes of human thought in the early chapters provides a sturdy, cognitive lense which game designers can use to understand challenge. This book focuses primarily on social reasoning and the challenge which could be derived from that important facet of human experience, so far unexplored in traditional video and computer games.
   
   In late 2005 Mr. Crawford wrote an article for The Escapist, and online publication which is highly recommended to anyone interested in the cutting edge of the interactive medium. The article addressed appealing to the female demographic of possible players from the angle of utilizing social challenge to meet women on a common ground. The problem with this article was that it used a controversial science to make this point, and it was possible to infer a sense of sexism, where women are inherenlty social and therefore drawn to interactive soap operas, while men are inherently spatial and drawn to games similar to hunting. The real point is that social challenge will put games on a whole new playing field which both men and women can appreciate as art and popular entertainment. Thats the lesson taught by "Chris Crawford on Interactive Storytelling", along with some useful approaches to the design problems. Don't let politics stop you from glimpsing a revolution.



5. One day the games industry will look at Chris Crawford the same way the film industry looks at Joseph Campbell. He sets out the first few steps of a path that could revolutionize gaming - if only it is taken to heart. Some of his ideas are radical, some are controversial, but all are insightful. The only criticism I have of this book is that Crawfords brash and grungy tongue-in-cheek delivery might rub some people the wrong way (although, I personally found it refreshing). And that the book is too short.