Programming Books

I thought this book was excellent for those who have some idea of what programming is all about, but for the complete lay-person who wants to jump into programming, this book could be a challenge, but is entirely possible for anyone semi-experienced with computers. Probably the best VB5 book so far. Would be equally as useful in learning VB6 (except the new features of course).

I learned VB for the past two years and had acquired for more than 10 books for introductory of VB. It is the best book that I have ever read for novice VB programmer. I highly recommended it to all person who are interested in Visual Basic.

Unfortunately, I'd already spent close to $200 on other books before I came across this one. I needed a step-by-step, well-written, easy to follow workbook type of text which would approximate a training course, and this book is it! All other books I tried were too dry and technical, boring me to death while simultaneously confusing me. Only wish I could find more titles in this series. Warning - "homework" assignments assume you have VB installed. If you've got VB and a little programming knowledge, BUY THIS BOOK AND GET BUSY WITH VB 5! =D

I am fairly new to Visual Basic Programming, and was looking for a good introductory book. I found it! This book covers just about everything you'd want to know about the foundations of VB5, every event & object. GREAT BOOK!

This book is not really a tutorial. I thought it was meant more as a source of reference, but I sure learned a heck of alot.

I took a VB class this year and this was the book that my teacher had recommended. During the class, we had to use a crappy book called "VB made easy". I read the whole book and still didnt know didly about VB. Then I bought this book!!! If you want a book that teaches you hard concepts of PROGRAMMING, and doesnt hold your hand through step by step projects that dont teach you how to think on your own...buy this book!!! I actually thought it deserved a 4.5 since a couple chapters could have been improved. But what book can teach you everything perfectly? So I curved it up comparing it to all the others i seen. Cause it sure came close. Now I do mostly programming at work with what i learned from this book. My next one will be "Profession VB 5.0 business objects" Check out the reviews on that one!!!

I found this book to be extremely helpful as a novice in the world of Visual Basic. Mr Davis's use of graphics took a great deal of the guess work away and demonstrated what the forms and properties should look like.

This is a great book for beginners. His explanations are clear and concise. The source code downloads were excellent and allowed the user to compare their projects and judge your progress. I would recommend this book to anyone wanting to know more about Visual Basic.

This book is for the novice / beginner with basic computer skills and no real programming experience. The visual approach to teaching used by the author (particularly the extensive illustrations, graphics, and code examples) provide an easy, structured approach to learning. The book assumes that you have a connection to the Web to download code - no CD is included. If you are just trying to "get your feet wet" and find out about what can be done with Visual Basic, this is the book for you.

For me, the main limitation of this book is that it is intended for the beginner and treats most topics superficially. It is not a particularly good reference text. I was trying to author a simple medical calculator, and ended up purchasing a more extensive book (Visual Basic 6.0 by Halvorson) because the information was not extensive enough in this book. If you 1) want to create a full-fledged program that could be used at work or home, 2) have experience programming macros, or 3) otherwise are beyond the "beginner" category, I would buy something else.

I've bought other VB books that are more detailed, but they are often tedious for beginners. This book perfectly balances ease of use with enough explanations for you to understand what you are doing as you learn by hands on example. The best way to learn VB is by doing it hands on. This book has tons of exercises so youre not just learning the fundamentals of VB programming, but you are seeing it all in action, building small mini-programs as you go along. Very easy to use, well explained, great graphics on almost every psge. If you desire to really be a master programmer, of course you will need a more detailed reference book afterward, and lots of hands on practicing to keep your skills sharp. But there are many books out there for that after youre done with this one. By the time you finish this book it will give you a real sense of what it feels like to construct programs in Visual Basic, and you'll be ready to take your learning experience to the next level. If I could give this book 6 stars, I would. Good luck to you all

A good book for the beginner. I can read in less than 5 days. It covers perfectly most of the basic visual controls: button, dialog, menu, combo list, text box, timer, data control, status bar, MDI, SDI, set up control, environment ... The codes in the examples are short and simple, but they are good enough for your learning. If you have experience with other programming languages in a less friendly environment like unix, then this book is a quick way to catch the main idea of this language by learning the GUI quick.
It mentions no OOP, ADO and has no cdrom, you should look in other books. In fact, this book covers all the main concepts that you will learn in the introduction course of vb at the college, except it will take you 15 weeks and you can do a little more coding. If you have some programming experience and need a quick learn the controls of vb, this is the book for you. You will not regret for < [money]. Other books will be the next. This book will not make you sick by the size and lengthy words. I wish I can find some similar for visual c++. Thank for any hint!

If you want to sit down and quickly get an understanding of Visual Basic, this is the book.

It favors readers who have limited programming experience, but it is not too simplistic. Readers who are experienced in other languages will find that they can just move through it a bit more quickly.

You start writing Visual Basic code on the first pages, and subsequent exercises build on what you have learned. As you go through the chapters, it provides enough clues to help beginners remember to change the name of new forms they create without boring more experienced programmers with endless step by step repetitions of how to start a new form!

Having ready many "How to..." books on Oracle, Access, Linux, WindowsNT, etc. I had become pretty frustrated about how much the books cost and how little I learned (largely because they were too poorly written to stick with them for even a couple of days). This book is a great value, and you really can learn how to program in Visual Basic from it!

It is funny how I was glancing at the books and this book Voice XML caught my attention. I was looking for a book like this. This is a great resource for Voice XML developers like me. The book covers wide range of topics. The book is an excellent hands on guide to build voice applications with Voice XML 2.0. I liked the VUI design tips throughout the book. Great job!

This book is an excellent resource for a VoiceXML developer. It covers a wide range of topics in detail and has some excellent VUI design tips. I love the cross reference of voice technology companies and the services that they provide.

This is the best VoiceXML book I've seen. Most VoiceXML books try to do too much: talk about voice hardware, telephony, the history of voice, tts, as well as be a VoiceXML reference. The weakness of these books is that one or more of these sections reveals that the authors do not really command the knowledge needed to make these sections useful. This book also attempts to do these things, but for the most part is able to carry it off.

If you're looking for a reference, this is the book to get. The reference section is current VoiceXML 2.0 (October 2001), which is an advantage in and of itself. But the real strength of the reference section is its depth. Each element, (e.g., , , ) has an entry for syntax (how to invoke the element), a description (what the element is used for), a thorough discussion of its attributes (that is, a description of the attribute), a usage statement (the elements parents and children), and an example (a snipet of complete code that uses the element). The examples and discussion of attributes really set this book apart from its peers.

There is a brief discussion of the architecture of a VoiceXML app, and a couple of paragraphs discussing the differences between VoiceXML 1.0 and 2.0.

The book also gives, contrary to my expectations, a history of the voice industry, a history of VoiceXML, and a discussion of players in the industry. What makes this book's treatment of these topics unusual is that the authors (particularly Kunins, I suspect) actually know these fields. I don't normally want these sections in a reference book (it just adds bulk around the section I really want) but I found them quite compelling here. I learned quite a bit from reading them.

The book also contains sections on Dynamic VoiceXML, Security, Voice App Life Cycle, VUI Design, the Future of VoiceXML, and a case study. I haven't read these sections yet, so I can't comment on them. I do know, however, that the sections I have read are sufficiently superior to make this THE VoiceXML book on their own.

If I were to criticize the book, I would fault the authors' lavish praise of TellMe (this is minor and not unexpected) and the examples in the reference section. The examples are quite good for someone learning VoiceXML, and the authors are commended for including them. The fault (albeit a minor one) is that they are fairly vanilla. So, while I would have preferred more examples, I concede that such examples would make the book much larger and the inclusion of "advanced" examples to the exclusion of "canonical" examples would have made them less useful to developers learning VoiceXML.

Overall, if you are going to own one VoiceXML reference, THIS should be that one.

This is a summary of the full review available at:
http://voicexmlplanet.com/reviews/vxmlbook.html

In short, this is the VoiceXML book I wish I had written. The authors have produced a comprehensive title that includes gems that could only have originated from masters of the craft.

My only complaint is that the book is a bit too biased towards Tellme (one of the authors is an employee), but this can be forgiven based on the quality and depth of the content.

My judgement is that this book is the most well rounded in-depth book on the topic that's been published to date. I am very happy with the mix of content, summaries of important concepts such as linguistics, speech recognition, and speech synthesis, as well as the in-your-face examples and complete reference. In fact, I liked it so much that I will probably be using it as a standard reference in my company's VoiceXML training course.

I was mislead by the accompanying great reviews for this book. Having bought and read the book I find that it serves more as a reference than to illustrate how VoiceXML can be used through example applications. But I should admit though that this book does a good job of serving as a reference. I also bought "VoiceXML: 10 Projects to Voice-Enable your system" that helped me to come up to speed to do a VoiceXML project.

This book was definitely worth the money. While it did not have me creating extreme UI modifications right away, it did provide the stepping stone i needed to go on and eventually learn to write bigger and better addons. The book give very useful information on Lua in general and then goes in depth to explain exactly how to program in World of Warcraft.

I would recommend this book for anyone wanting to learn to create addons. While it won't boost you to a master of creating addons, it will give you that stepping stone that has seemed to be missing since WoW's release. The API reference also helps anyone interested in writing addons, whether they be novice or master.

this book is for those who are not wow savvy. If you are you are probably wasting your time. My son was not as impressed with this book as other books he has received.

If you want to write that killer add-on for World of Warcraft that nobody has quite gotten right yet, then this is the book to start with. I have been programming for many years but this book has a lot to offer to a kid just jumping in to the exciting world of code smithing or an old pro who just needs to know what Lua is all about. It is written by the guys that are doing it not just talking about it. Just the sections on the API reference is worth the price of admition. If you want to be WOWed by WoW, then cozy up to the glow of your nearest monitor and dig in.

If you ever wanted to make your own add on's for the wonderful game of WoW then this book is for you! It tells you everything you need to know to program for WoW. Great book and great buy. Definitely one that will be read numerous times and used as a reference for my programming efforts for the game. (made an alarm clock to tell my kids to get off the game at a certain time) Great book!

Do not let the cover fool you. This book is HUGE with 1022 pages full of references, examples and more.

I am a beginning programmer in lua and WoW addons and I have other programming languages under my belt which helps me out. This book will explain it to the novice as well as provide an excellent resource for the advanced programmer.

You cannot beat the price for the quality you get. I have paid twice as much for books with 1/2 that information.

I would recommend this book to anyone wanting to make their own WoW addons.

Attention Michael Pachis and others who purchased this book in 2006: I am the book's author and when I saw your comments, I contacted my publisher. If you purchased a copy recently and received it in 3-hole punch format, send me an email and I'll put you in touch with the publisher. They have a small number of perfect bound copies they can send you instead. Use the email address on the right side on my personal web site (kensall.com) home page. I hope this helps.
(I gave this 5 stars simply to not impact the book's current rating.)

This is an excellent book to understand, develop and code XML. However, in the parsing discussions (chp 7-10) an understanding of OOP and Java programming are almost required. Other than that, it is an excellent text.

I want to warn customers that the publisher has gone to a "print on demand" publishing model and this book is not delivered as a paperback, but as eleven hundred three hole punched loose leaf pages! This leaves you with the task of finding a binder after paying 40$ for the book! Since it is book size (8 x 10) it awkawardly fits into a standard 8.5 x 11 binder, not very convenient for reading or transporting, and you need the binder to be 3.5" thick to fit the book in the binder.

I gave it five stars for content, but this new method of publishing gets zero stars.

This book is not an "how to" guide, nor does it claim to be one. I mean by this that if you are, say a Java programmer looking for a book that concretely shows you how to integrate xml with Java then you would be better off with one of the so many Java/XML books on the market.

However, if in your work or your studies you feel that you need to gain a more thorough understanding of the W3C specifications related to XML, then this is the book to buy.

All the W3C specs are available for free on the web. The trouble is, W3C documents are designed to provide a precise definition of a standards, they are not designed to be especially intelligible by mere mortals (however technologically enclined). Some are quite readable, others far less.

Firstly, I really like that this book present all the relevant specifications and working drafts in perspective. Secondly, I found that it does a remarkably good job at translating these specifications (without simplifying them) in understandable terms.

In my work, I am interested in gaining as thorough as possible a view of XMl technologies and this book helps me greatly. I also like the fact that it present a well-organized bibliography at the end of each chapter (sadly many computer books from Wrox, O'reilly, Que an like don't have a bibiography as if to say "everything inside this book comes straight from the author's mind. DO not look any further).

I have reviewed for myself around twenty XML books. I found this book to be one of my top favorite. I recommend it especially for:
- CS students or programmer with a theoretical bent.
- anybody who wants to get a thorough overview of W3C standards.

Where to start? With the concise history of where XML came from and why each design decision was made and how the evolution of specifications took place over the years, or the thorough explanation of all the XML specifications, or the programming and parsing aspects of XML and metadata, or the cool XML timeline poster towards the end of the book? This book has much to offer any person interested in finding out what XML is and why and how it has changed our world.

Kenneth B. Sall, the author of this book, organized this book in a fashion where each section could be studied on its own, and if there are references to the previous sections, they are appropriately mentioned. This way, one does not need to sit down and cover this 1000+ page book cover to cover to realize that the topic of conversation is. The stage is set at the beginning by the author commenting on the fact that XML can describe everything under the sun, even the kitchen sink:

"XML: ... maybe it's everything but the kitchen sink? Say, have you heard the one about the XML Kitchen Sink Language? ..."

I have been working with XML for sometime now, and I am still amazed at how it has grown and expanded in to our everyday lives in the past few years. One can spend months coming up to speed with the specifications and the XML "realm", and that's not enough. This book does not even cover, in a great detail at least, the Web services realm. That alone is a couple of thousand page book. The background topics are essential to any reader: basic XML syntax, DTD, Canonical XML, Namespaces and XML Schema. Once you have these topics covered and well understood, you can jump around to any other part of the book, displaying XML data for example or XML programming API's.

One can spend a couple of hours trying to figure out how these specifications fit in, but the author hs already done the job with a very useful picture inside the cover page. What's your forte? Cascading Style Sheets to convert XML data into a PDF document for example, or an XHTML document to display on a web site? XHTML is also covered in length, if you do not know that is and what it offers over the plain old HTML.
My favorite topics were probably the authors explanation of the XML parsing and the available API's and resources. SAX, DOM, JAXP and JDOM are covered in great detail.
* SAX - the API that started it all. Minimal and light-weight. Fast and event driven.
* DOM - Memory intensive, complex, but very powerful. It's a tree based model, and the tree represents the whole document.
* JDOM - java specific. Can be used with either DOM or SAX.
* JAXP - java specific again, but easier to use than JDOM.
There are also a number of C++ XML parsers that the author touches on such as the Apache Xerces, C++ SAX and many others, but the main topics revolve around the four most popular parsers mentioned. These sections are mostly tutorials and how-to's. Each parser is used in an example and example is analyzed piece by piece. DOM is covered in more detail due to the number of levels (DOM level 1-3) that it has. Since DOM is more powerful and more complicated, the topic is a bit more advanced and would require more attention from a novice. If you read thru the SAX chapter and understand it well, DOM would not be that much of hurtle, but make sure that you read understand SAX first. Java centric API's including XML-RPC, JAXB, JDOM, JAXM are covered by the author to depict how XML can be used and how it would benefit the application - and developers in-turn. The icing on the cake is when K. B. Sall outlines the differences between SAX, DOM, JDOM and JSAX. He talks about each of the technologies in detail, tell you what the advantage and disadvantage of each one is, and then it compares them against each other. By the time you are done reading these sections, you would become an expert in XML parsing and programming.

XLink and XPointer. How can one leave without these two core technologies and tools? They are truly remarkable; easy to use, light weight and easy to learn. Well, they are well covered - as you would expect from this book. One thing about these topics is that they could be very abstract and need examples, and we got lots of those. The example depict the efficacy of how one can use XLink to create complex connections between sets of resources, even though you do not have a write access to those resources. This is very handy and resourceful technique is you need to build an e-commerce site. With XPointer, one can locate individual XML elements, set of elements or even a range of XML data between two points. The ability to specify "range" of elements is where the true power of XPointer is revealed.

The references, the related resources for each topic, simple to complicated examples and a CD filled with goodies, source code used throughout the book and the W3C specifications at your fingertips outline the some of the other benefits of Kenneth B. Sall's "XML Family of Specifications" book.

This book is an excellent resource for learning AspectJ. It is perfectly organized to take you from beginner, novice, to expert as you move through each of the chapters, just as you might expect if you were taking a class in AspectJ.

The author's presentation of the material is straightforward and easy to follow, and his examples are not too involved that you lose track of what's going on. Furthermore, the author has an excellent grasp of the language and is really able to show off the power AspectJ has to offer.

What I really appreciate about the book is that he focuses not just on coding, but also on design; I'm a software engineer and am very pleased that the author discusses an aspect as something to be used elegantly, as part of a well-designed system, rather than just another tool that can be abused. He even discusses several new design patterns that AspectJ makes possible.

I truly recommend this book!

I met the author of this book this weekend, and saw him give a presentation on this material. Finally, a book that shows real uses for AOP.
I have been watching AspectJ since I first saw it about a year ago. My first impression was that it was 'cool', but was worried about giving developers more rope with which to hang themselves. Yes, it was cool, but the most practical examples you would see in demos were thing like 'logging'. I was worried that it would just lead more more ways for junior engineers to 'convolute the code', without bringing much benefit for that risk.
The material in this book, ALONG WITH the support the author had from the Eclipse IDE changed my mind. Finally, there were some real examples involving transaction support, JAAS, exception handling, and more. Furthermore, he addressed these topics in the real-world sense of refactoring existing code to prove his points.
If you aren't using an IDE that gives you some support, then I still have my concerns about 'convoluting' your code; but I am more convinced than ever that AOP concepts are worth putting into my mental toolkit. I have no doubt that the way aspects 'inject' behavior into code will reduce our development time, and make our code behave more consistently (no errors because of inconsistencies in the way common things are handled). If you can add one more ball to the things you 'mentally juggle' while developing, add AOP concepts. This book will help.

I have got this book at local Austin Java User Group meeting. First impression: different cover. Most of Manning books are either greenish or almost black-and-white. This one is yellow.

Part 1 provides really good introduction into AOP. This is the first book I have read on AOP; all stuff I have seen before was online or magazine articles. One interesting fact is that this book took a while to consume, compared to the usual two-week cycle I have for technical books. I guess the reason is that the book has more substance than most of the techincal books and Mannigs does not try to pad their books with API references and other stuff that can be easily found online. After the chapter goes through AOP concepts, it explains AspectJ in application to those concepts. Basic syntax as well as some advanced techniques are explained.

Part 2 has examples of basic applications of AspectJ. Of course it starts with the mandatory logging implemented using AOP. Not a very good example in general, since logging is not really a cross-cutting concern, but works for illustration purposes. Other two application areas discussed in this part are implementation policy enforcement and optimization (pooling and caching examples). Policy enorcement part is really interesting, especially if you are into call patterns.

In general, every part follows the same pattern: first the author discusses the conventional approach, then explains challenges of the conventional solution, provides AspectJ-based solution, and gives one or two examples. Very clean language, easy to follow.

Part 3 discusses advanced applications of AspectJ. First it delves into design patterns and idioms of AOP; it's not by any means AspectJ-specific, so would be useful for any AOP implementation. Examples of patterns are providing thread-safe implementations using AspectJ, implementing security (very interesting discussion on JAAS), transaction management, and implementing business rules using AspectJ. The part ends with AspectJ usage in different development phases.

Two appendices: description of AspectJ compiler and Ant integration - only 15 pages for both. Useful as a reference.

Overall impression: an excellent book. Definitely worth reading, even if you are not into AOP yet.

I loved this book, first of all the introduction is the most interesting presentation of AOP that I ever read.

The other chapters are very good too since based on use-cases very easy to reproduce on projects...

A book to have is you want to learn abour AOP (even if not interested by AspectJ per se...)

AspectJ In Action is a great book to use as an introduction to Aspect-oriented Programming. However, AOP is not for developers to whom Java and OO are still new. Without a comfortable understanding of classes, polymorphism, and encapsulation AOP will only further confuse things.

With that said, AspectJ In Action is a wonderful book filled with plenty of examples and explanations about the well-lit areas of AOP as well as many of the dark corners. I enjoyed reading this book because it starts out with the fundamentals and works its way to more and more complex uses of AOP without getting bogged down in language tangents. Also, the direct application of AOP in real Java design areas is very helpful in getting a better feel for when and how AOP can be applied.

I am looking forward to Ramnivas Laddad's next book!

This book is clearly a "must have" for anyone developing with VFE. Despite spending a fair amount of time on the VFE Tech Support Conference, attending 2 VFE DevCons, etc., I have found this book to be invaluable. In particular, I like the narratives on the Instantiation of the Application object and Form, along with the discussion of various key properties and methods of the major classes. To the extent that one spends time actually studying these narratives, properties, and methods in conjunction with stepping thru the code, I feel this will reap rewards in the form of better productivity and higher quality applications. For those who aspire to get some depth of understanding of this framework, this book is for you.

This book is a "must have" reference for all Visual Foxpro programmers who use Visual FoxExpress. The information in this book will save many hours of development time. I highly recommend it.

I have read this book twice and will probably read it again. Everytime I read it I gain a little more insight into this great foundation and n-tier development. I especially like the explanation of the step-through logic in Chapter 10 and the explanation of each method in the various objects.

I think that if you buy Visual FoxExpress and buy this book, you will reduce your learning curve by several months.

This book is great for both new users of the VFE framework and experienced users alike. Not only does it provide step-by-step guidelines for building your apps with the VFE framework, but it also contains numerous tips and tricks for experienced developers. A required reference for all VFP/VFE developers!

This book is a crucial part of my reference library. Although Visual FoxExpress comes with good documentation and a sample application, it lacks the step by step walkthrough with explanations on the thoughts behind the concepts. This book fills in the blanks very nicely and helps the reader to gain a better understanding of not just the "how" but also the "why". The authors do not hesitate to inject their own observances and opinions about working this powerful framework. This makes it an interesting read as well as a good reference.

I confirm all that has been said.

It is the first source I have found that explains building the linux kernel in a way that makes it easy to understand. While you might be able to find this information on the net, this makes it easy to get an overall view of what is going on.

It is easy to read, and has great references. Well worth the price.

This book is very well organized, and provides a good level of detail of the topic. I do recommend it.

I am an experienced embedded developer that just inherited an embedded Linux-based project already in progress. As there happens to be no one else at my company with any embedded Linux experience, I automatically became the de-facto Linux expert and I needed to come up to speed on a lot of topics very quickly. I found this book to be an excellent survey of the must-know topics for the embedded Linux developer. It also contains many references to the most definitive sources of information on the various topics. Highly recommended for coming up to speed on embedded Linux.

For those engineers who start their first embedded Linux project, this book is a must have. The book is not for those who want to understand how kernel runs but it gives you the most important concept and work flow to bring up the OS on your development board. The author also provides a useful further reading list in case you want to dig more. A very practical and clearly written book and I would recommend it to those who have solid experience in embedded development but just start to explore in Linux.

This book, the CALAO SYSTEM USB-A9260 card, an eeePC and a cross over cable is all that you need to study embedded system everywhere (even along the Seine river in Paris - yes I did it !).
The chapters about the U-BOOT bootloader, the BUSYBOX embeded Linux and an extra piece of information on the JFFS2 file system are welcome. If the cross-development environment chapter had been about BUILDROOT, this book would have been THE BOOK for the present embedded Linux based systems designers.

I ordered this book to serve as a reference for my symfony work. It has been an excellent reference guide to symfony, though it is not meant to be a "Introduction to.." or "Getting Started" book. I highly recommend if you work or have a solid background in symfony and need a handy desktop reference manual.

This book is really the definitive guide. It covers everything you need to know to build a web 2.0 application with symfony. It is written by the people behind symfony, so the book is extremely detailed and has a great format that makes it easy to understand. Well done.

The books contains all the information you can find in the online manual on the website of the symfony project.
If you know this before (and I did), the book has the same quality like the online manual, in my opinion a very good one.

I'm a freelancer that was in search of a framework that would allow me to expeditiously develop applications for my clients, without sacrificing reliability. After researching several PHP-based MVC frameworks, I landed on symnfony due to its comprehensive set of features, strong OOP support, PHP5 utilization, and (very importantly) the great documentation. Yes, this book is available in web format online - but I'm very glad I made the purchase so I could learn the framework as I traveled, and it's much easier to use as a reference (I have it sprawled across my desk as I type this review). If you're looking for a great framework, I'm convinced symfony is it. And if you're looking to learn symfony, and have a resource as you build your skills, this book is what you'll need. The only caviat is, if you have no Object-Oriented programming experience, I would recommend you pick up "Objects, Patterns, & Practice" by Apress before learning symfony.

Well written and understandable for such a large chunk of software. You can be the judge yourself, of course, by reading it online before you buy the hard copy. I'd definitely recommend having the real thing if you're just starting with symfony though.. you can't dogear or bookmark the online version.

I'm not an expert in either Interface Design or Programming Methodology, and I've only read a little bit in these areas. As I read this book, I found myself thinking: "You mean this approach isn't standard practice already?"

After reading Ellen and Alan's description of how a UI Designer and a Developer should interact with each other, it just seems so obvious that everyone should work this way. User needs should affect architecture, and technology constrains design--how hard can it be to understand that? But the implications--design and development are iterative, and ongoing user testing is critical to the iterative process--could change the way some people think about programming projects. (The old Specify, Design, Program, Test, Release process seems somewhat naive in retrospect.)

The book has a kind of fun and lively feel to it. It's clear that the authors were having fun telling their various stories, and were excited about illustrating their points. The writing is casual, which made it amazingly easy to read.

On the other hand, once the informal style sold me on the overall approach, I almost immediately wanted a more rigorous treatment. I'd have loved an Appendix that summarized the formats of the various documents, for instance, and perhaps one that reviews the process flow diagram used at the beginning of the later chapters. (As a former academic, I found myself wondering as well about the independence and completeness of the Design Guidelines, too, but that's my quirk. It's probably not an issue most readers would care about.)

I think this book could become one of those that inspires a sort of religious commitment to its vision, and that that would probably be a very good thing.

First let me tell you this is an interaction design (or user interface design) book, since the title of the book doesn't do this job well.

This is one of the books that have great impact on me. I agree with the review written by Kevin Mullet (printed on the book's back cover) that the ideas presented in this book are a bit "dangerous". It is dangerous because they are not the common practice yet. If people want to follow these ideas, they need to have changes. Changes are always dangerous to many people.

Those "dangerous" ideas include:

- Build fewer features but build them well. (The current practice is to build as many features as possible so that marketers can list those features for promotion. Is a product easy to use? Everyone can claim that since there are no criteria for such a claim.)

- User interface design should drive the system architecture, not the other way around. (Modifying system architecture is always hard. If we want to support a certain interaction afterwards, the architecture will probably can't support cleanly, if at all.)

- Technology should be used for user needs, but not for technology's own sake. (Visual design should also be treated the same.)

Last but not least, this book shows that user interface design is actually science but not art. We don't need a graphic design degree to be an interaction designer.

As an IT project manager supporting web applications, sites and portals, this book summarizes the story of my life. Not just a must-read, but a godsend for application developers and UI designers -- two groups who traditionally don't always see eye-to-eye or face daunting communication challenges. Can't we all just get along? Yes! This book tells you how, using simple, easy-to-understand language and real-life examples. End users and customers will thank you for reading it.

I highly recommend this book as an invaluable resource for anyone currently in, or looking to enter, the instructional design field. The authors have successfully been able to present information, which can often be dry and complex, in a clear and easy to read format.

I have a read many books in this area and they have been a fantastic cure for insomnia. This on the other hand is a compelling read from start to finish. Many of the concepts presented will not be foreign to people that work in this field or in the area of product development. However the logical order and detailed examples work brilliantly to drive home the principles.

Publishers in this area should use this book as a bench mark for design and layout for its susinct and logical passage. Thank you very much Ellen and Allan for such a useful tool!

This book has many examples of good and bad web pages and also consumer products. What it covers is seemingly obvious, but apparently not realized by many. It shows how users and designers can work together for optimal result. It should be a required reading for anyone doing user-interface designs. It is good that they actually have a good free product, HUBBUB ... .that was created using this design philosophy.
I didn't give it a 5-star only because, to me, the section of their HUBBUB experience and the conclusion was too long and could have been made more concise. Also, it was disappointing to see their product not following their own design goals well enough, which seemed to make the book less effective.