Human-Computer Interaction Books

This book was a fascinating autobiography of how becoming a `cyborg' made Chorost more human. A cyborg is "shorthand for cybernetic organism..., and is defined by WordNet as `a human being whose body has been taken over in whole or in part by electromechanical devices'" (7). He approached the book by explaining the human side of having a computer control one of your senses. Instead of thinking about the fact that he would be able to hear again, he was having trouble with the fact that he would not be in control of his hearing. It is a unique story detailing the process of cochlear implants, as he describes his fascination with computers, and his witty sense of humor all of which was complemented by his scientific background. It is a heart felt story that showed the life of a man adjusting to becoming a `cyborg'.

Chorost had been partially deaf his entire life relying on hearing aides to allow him to hear. The story starts off describing the tragic day of losing what little hearing he had left. He gave such distinct detail that you know exactly what he is going through. While he was thinking his hearing aide batteries were dying, he actually was going completely deaf. His hair cells are still intact and can be triggered with electrodes, which led him to be a candidate for cochlear implants. Contemplating the idea of having a computerized chip in his head was overwhelming and he gave an interesting point of view of his dilemma. To him, it was more than being able to hear again which is how most people would view cochlear implants; it was losing part of being human and being controlled by a mini computer scared him. The same kind of technology he was obsessed with was going into his body.

Throughout the book he talks about the struggles he had as a kid with his hearing problems and really explains his way of thinking. He really allows the readers to involve themselves with the story, and seems to say exactly what is on his mind about his new implant. He speaks of the foreign object in his ear and just spits out whatever thought come to his mind. It gives a vivid imagination of what he is going through and the side effects, so to speak, of a surgery of this kind. It shows the implications and hardships that have to be overcome to hear again. "The essence of the cyborgness is the presence of software that makes if-then-else decisions and acts on the body. It's the `acts' part that is important." His concern for not having control over one of his sense is a troubling matter for him. He is very skeptical about being `switched on' and when he reenters the world of hearing he feels like he is playing a guessing game in deciphering their words. The daily struggle of dealing with his new computerized hearing system was apparent.

Chorost went into detail about the anatomy of the ear and how the damage actually occurred to allow the reader to understand how the cochlear implants work. He keeps referring to being less human due to the non-control of this computerized system attached to his skull. He says sixteen electrodes are working to stimulate the neurons in the cochlea to decipher sounds control his hearing. "It was strange that I should be so stubborn about perceiving the world in one and only one way, because the exact thing I loved about computers was their infinite malleability, their ability to create worlds out of imagination "(75). After switching a few electrodes off, he was finally able to hear and distinguish sounds again like the difference between male and female sounds. "The software had not changed. The world presumably had not changed. What had to have changed was my brain" (86). He believes the brain is plastic and "when a part of a body changes, so does the area of the brain that controls it" (87).

He describes the everyday normal stuff he goes through as not being so simple and easy. For example, getting a cell phone was a large task because he has to find one that would not interfere with his processor, one that would enter a patch cable and then of course one that works in the area he resides. He even talks about the difficulty of his sex life and how that works out for him. His openness about his personal life might surprise or offend some readers, however, I loved it. This is because that is exactly how I write and would like to read a book like this. It allows for a deeper understanding of what the author is going through by learning various aspects of his life. He also goes into his longing for a group of good friends and the different ways he goes about doing it.

By adjusting to his implants, he realized they helped in more ways then he ever imagined. " The computer invaded the sacred domain of my body, yet to my own astonishment we learned to work together as a total system, mutually changing each other in the process. I fed it lithium-ion batteries; it fed me electrons. I altered its software; it repartterened the dendrites in my auditory cortex. We have literally reprogrammed each other" (156). "The one hundred and forty thousand transistors in my skull give me sound, but they cannot make me listen. Its only when I listen that my cyborg technologies make me a better human being" (183). Over the years, his hearing improved with the software updates. He attributes this improvement to neural plasticity, as his auditory cortex is completely rewired due to the increase stimulation.

I thoroughly enjoyed the writing style of this book. As a partially deaf girl, I can closely relate to the author. The way he described hearing aide batteries dying and the way it sounds when you put a new one in is exactly what goes through my mind. It was cool to see how he really spoke what was on his mind and that other people know what I go though on a regular basis. I also enjoyed his detailed description about the cochlear implants because I was never sure how they actually worked. Due to his writing style, to "just read this book" is an understatement, it's more like you experience the book. This book was provoking, and well written with a unique writing style that was an enjoyable and educational read. I would definitely recommend it to anyone that wants an extraordinary read.

Rebuilt: My Journey Back to the Hearing World

Michael Chorost does an excellent job of explaining the *human* side of cochlear implantation, offering a perspective that just understanding the mechanics does not. I found myself drawn into the book as he described his feeling of despair, as the little bit of hearing he did have mysteriously failed one day.

Chorost also provides an insightful view of life in the Signing community, and how the implant may ultimately result in its demise. While I don't agree with those who call this 'genocide', those chapters provided an interesting and thought-provoking point of view.

The book is not flawless. Sometimes the author's meanderings on life as a cyborg seem to have no clear destination in sight. But the perspectives provided more than made up for the occasional drift. As someone interested in Augmented Reality, I viewed these chapters as a sneak preview of what the next few years will bring.

I also found Chorost's discussion of his sex life to be gratuitous, by which I mean that had it been omitted, I wouldn't have finished the book saying "That was a great book; I only wish I knew more about what he did in bed." But others may find these passages make the protagonist more human. I guess that's what makes horse races.

All in all, definitely a worthwhile read if you're interested in getting beyond the electrodes and MIPs and understanding the human side of all this.

This is a very well-written book but it was very technical and dry in places. I still ordered my own copy of it since the subject matter is an important one for my family.

I have a CI too and I don't consider myself to be a cyborg or part computer. I consider myself lucky and fortunate to be in a time where this is possible. I lost my hearing suddenly before we left for a trip out west to the Rockies at the age of 34 and a young mom of twin boys that were not even two yet. Scary? Oh you betcha. I got mine for a variety of reasons but mainly because I needed to hear. Like the author of this book, I had grown up wearing hearing aids. So getting the implant was a necessity for me and one that I am eternally grateful for.

This book is very interesting in the aspect of technology and how cochlear implant works. This book would be perfect for my husband and dad to read since they love anything technical. But all the references to science fiction turned me off as well as his personal stories about his dating/sex life. I honestly don't care about that so that is why this is rated a three stars instead of a four. If they were trimmed out or modified, then this would be a four.

I really do appreciate the section on how the Deaf Culture changed from the year of 2000 to 2004 (or something like that). I did watch the movie, "Sound and the Fury" and for the first time in my life, I had a glimpse of what the Deaf Culture is about (not that I agree with it). This author went into more details (and got me to order more books on that subject) about something that has changed since I was a child. As a mother of a HOH child who may be a candidate for a CI, this book is helpful in sharing information that I may not get otherwise.

This is an interesting book and a great introduction to cochlear implants and how it affects one man's life and how it affects society today. It is a good read and a helpful one.

4/28/08

Excellent book for the hearing impaired and non-impaired alike. Much detail on living and learning to adapt in a hearing world. Highly recommended.

When I started going deaf, people often said "Well worse things can happen". That is certainly true. Deaf is not dead. But there is a connection that maybe only a poet should make, and Michael Chorost was deaf and is a poet, so he can speak with a poetic inner voice that rings true, even though I will never be able to hear anything really ring again. For now, I have not yet gotten a cochlear implant and simply struggle to hold on to my rapidly diminishing hearing by increasingly expensive and often frustrating hearing aids. Michael's story has helped me to better accept my loss: technology cannot give me back my hearing the way it was, but it can help, and I am certainly not dead. Indeed, compared to Michael and many others, I am really very lucky, since I had many long years of good hearing, and now I look forward to more years of great living even with the hearing loss. I thank Michael for helping me to gain a measured, realistic, perspective on my deafness. This is a book about living, not just about living with a disability.

Finally someone noticed all the small differences in System Administrators lifes that require a different approach to time management.

Plus, a sense of humour and accurate advices.

Time Management for System Administrators is a book not only aimed at system administrators but also other task and interrupt driven employees early in their career. It presents a core concept of use to anyone struggling with a "never ending TODO list of doom" both for business and personal tasks. Some of the information is of a very basic nature such as "do short tasks and important tasks first". Part of this, however, could be Thomas Limoncelli's writing style which is detailed almost to a fault. It is, however, a very easy book to read and I found myself going through quite a few pages in one sitting.

On the negative side the analogies the author uses to try and explain time management in computer terms get a bit thick at times in the first few chapters but soon they run out and are no longer in the way of the points being made. Two other somewhat awkward chapters are the Stress Management and Automation chapters. Is it worth the time to write (or read) a chapter to basically tell us to occasionally take a vacation and to get a massage? It seems like filler to pad out the book. Similarly, the important take-away point of the automation chapter is to, well, automate things! However the chapter contains an overly specific set of shell programming tricks the author has learned over the years. These are of course presented as examples of how to automate, but the amount of time spent on details and anecdotes makes this chapter also feels like pad. The time spent in these chapters could have been better spent on the core points of the book.

What is the most valuable information in this book? The core technique is what the author calls The Cycle System. This is a way to manage your TODO list so at the end of each day every item assigned to that day has been addressed, if not necessarily completed. It's a very useful technique for learning to plan, to ensure you follow through with completing tasks and to improve your sense of accomplishment that you are managing your workload. Interestingly the author has always used a paper-based TODO list and calendar, so each technique of The Cycle System is explained both for paper and digital (PDA) methods. The Cycle System can help by providing a framework for managing tasks other than continuing to add them to an ever growing list, however it still requires a lot of discipline to properly schedule tasks in the future to avoid them all piling up on the task list for the current day. After several weeks of using the system it is certainly a workable method as long as you are honest with yourself on the amount of real work you can accomplish in a single day and you dedicate a good bit of time on a regular basis to future planning and scheduling of tasks that aren't high priority or due immediately. Unfortunately, the author doesn't go into a lot of detail on techniques to handle the issue of building up a backlog of low priority tasks other than to suggest daily, weekly and monthly planning times to reprioritize and reschedule tasks. The issues of email management, interruptions, unexpected tasks, request tracking software and even life goals are addressed. This portion of the book is where the true value lies and it provides a good amount of information.

If you currently have no structured task management system this is a great resource to start with. You'll certainly come away with a wealth of information on getting a system in place to start to manage things. If you forget to complete tasks or tell someone you'll do something only to forget it when the next person you run into starts you on a new problem, then this book will be very useful to you in how to manage interruptions and always follow through. If you are fresh out of school and you're in an IT job where tasks are starting to pile up, this book will be of even more benefit to you with its stories and broad IT specific topics. As such I would recommend this book to anyone in a task and interruption oriented job as a basic primer on how you should be expected to manage yourself. If you are in a computer job, so much the better, but regardless of your line of work you can still learn a great deal.

Ranked at four stars due to the issues discussed above, but still very highly recommended!

I was skeptical at first, but I followed the advice in this book, and BOY HAS IT MADE A DIFFERENCE!

I picked up this book when it first came out, as I was already a fan of The Practice of System and Network Administration.

It's been three years, and I'm no longer frazzled. Users no longer call me angrily wondering why I forgot to do such-and-such. I (hardly ever) forget to renew service agreements and run regular maintenance.

I cannot recommend this book enough, especially if you feel like there aren't enough hours in the day, if you work late, if you feel like your users are beating down your door.

Another thing about the system described in the book is its reliance on a paper-based organizer. I had tried and failed several times to use electronic methods. I'm a sysadmin! I should be able to use computers for everything! Being given a sort of permission to use paper for what it is good for helped me out a lot.

As a DBA, I found this book extremely useful. It's easy to read and has practical advice that works. I was a bit demotivated at work and this book helped me spring back into action.

Some of his quotes I try to remember daily; one of my favorites is "perfection is a real time waster" because it's so true!

Making to-do lists and setting goals is an integral part of time management and this book shows you how to do it properly. A+!

Tom Limoncelli is a well-known system administrator, author and orator. He speaks at conferences around the globe on issues ranging from firewall security to time management. He has also published papers at conferences such as the Usenix LISA on a wide variety of topics including innovative firewall techniques, coordinating massive network changes, models for improving customer support, and the security issues related to firing your system administrator.

I like the book "Time Management for System Administrators" because it is written BY system administrator FOR system administrators.

The book covers not only the general time management principles, but also valuable advices for system administrators: how to make use of automation, how to cope with multiple customers, bosses and tasks, and so on.

In addition to this book, I can recommend the other great titles that I liked much: "Never Check E-Mail In the Morning" by Julie Morgenstern, "Getting Things Done" by David Allen and "Time Drive" by Gleb Arkhangelsky.

This is a recommended book to read for people who would like to read about statistics and maths. People with few knowledge about these sciences will find it a bit difficult to read.

This is the best book I have found for a general study of the of neural networks. I found this particularly useful when looking at how to write my own NN frameworks. The depth of the mathematics allowed me to easily answer questions like: 'what if I replaced function abc with xyz'. I have found other texts failed to show key mathematical derivations, or to explore the subtleties of what the maths imply.

The book covers a plethora of topics from simple gradient descent through second order techniques and conjugate gradient, through to the use of 'bayesian techniques' (basically confidence intervals on network outputs), monte carlo techniques etc. Similarly error functions, non-linearities (sigmoids, softmax etc.) and data preparation are all treated.

The extensive bibliography also provides excellent references for further study, (a whos who of the field, as well as actual titles). My copy is now dog earred from frequent reading.

The theories of NN and PR are quite difficult to understand. But this book makes them much easier. The author can explain the concepts without using too much formula. If other authors could follow his step then the life is much easier!

If you want a very good, intermediate introduction to pattern classification this book must be on your bookshelf. It even does a very nice job explaining the EM algorithm in a few pages! Basic calculus is all you need to understand the book. A must read.

Mr Bishop's book is very well written and contains a lot of useful information on neural networks. It is outlined well and progresses in a logical form. If, however, you are looking for a book that gives discussions with concrete examples of neural networks applications or set ups, you will be sorely disappointed. The mathematical treatment is universally generalized with very few specific concrete examples shown. Even the exercises will not serve you well. The term 'graded' is used; however, that simply referes to the description of difficulty. There are no answers to these exercises, so unless you have a teacher or are already firmly familiar with the material, you will not know if you have completed them correctly or not. Even worse, the exercises are in general not written to reinforce concepts in the chapter, but in most cases extend the chapter material into new regions.

In summary, this book should only be purchased by someone already familiar with neural networks and their mathematical basis. Anyone else will be wasting their money.

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

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

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

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

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

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

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

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

I needed an easy to follow, yet comprehensive textbook to teach a class called Fundamentals of computers and the Internet. This book is simple, yet covers all the information a first time computer user needs--without being condescwending like the "For Dummies" series.

Good book for beginner, if you are just learning get this book.There are things in this book that took me years to learn by trial and error unfortunaely for me I only learned a couple of new things, but it did give me some certainty in what I did know. However Im now looking for a intermediate book which is what I really needed.

The book lives up to its reputation as being a beginners guide. Good resource for those now getting into computers. And, it also has some good steps for Vista too.

This a great book for aquainting yourself with your computer. If you are new to the computer world as I was you will find this book very helpful in taking control of your computer instead of it controlling you. It covers both versions of Windows: XP & Vista. I would recommend it to anyone just starting out. I think it would be safe to say it could save you a lot of time in the longrun and maybe keep you from pulling your hair out!

Like most people,i avoided the 21st century technology by continuly saying to myself it was not something i needed.I finally took the plunge,a friend set up my Toshiba A2125 and found the"Absolute beginners guide on your web page.It,s format coinsides with my 73 year old mindset.Congradulations Michael Miller

This is a benchmark book for interactive design. It separates the design process into information design, interactive design and presentation design. Those who head the process and focus on information design tasks at the beginning of an interactive project will find that costs are lower.

Information design changes are easiest at the beginning of a project and create large cost problems at the end.

If you have proceeded with good information design then interactive design and costs are much less difficult and less expensive.

Finally if you have made good information design and interactive design decisions, then you have a vast arrays of how to present the final product. It is at this stage the costs the highest with graphic designers, video producers, web developers, programmers and so on.

Read the book and memorize the process.

The book promised a lot based on previous readers' reviews and the publishing house's reputation but I was disappointed with its contents. The information is well presented but too simplistic. Lacking any further elaboration this book is of little use if you have some experience in the field of interactive design. A good brain-storming session at home would come up with the same findings of this book.

I have had this book for 4+ years. I loaned it to a friend once who didn't return it, so I bough another one.

Among the dozens of books I own and read on usability or project management, etc. this one is fantastic - a real stand-out.

The one drawback is that it's not as contemporary/up-to-the-minute as newer books. [shrug]

This is nicely organized, introduces important concepts and explains them in plain english. I used it as a textbook for a multimedia class and it was well received.

You will not find fancy tricks and designs, but you will get a good overview of multimedia, interface design and project management. It is 'outdated' so it is not suitable for experts but its information is excellent for an intro class, especially for people with little graphics experience.

For once, someone makes the distinction between information design, interaction design and presentation design. This book was invaluable in helping our division more clearly define our process for product development.

Jack Herrington's "Podcasting Hacks" (O'Reilly) is an excellent collection of tips, tricks, and explanations about making, publishing, and enjoying podcasts.

Although the book is primarily aimed at people who are creating podcasts, it also contains some info on the tools and techniques for finding and listening to them.

The O'Reilly "Hacks" books are structured as a series of specific projects, "hacks", that you can implement, but most every hack also includes a valuable explanation of the technology or expertise it uses.

The hacks in this book fall into both technical and non-tech categories. There's plenty on microphones, mixers and mp3 files. But also a lot on interviewing, blogging and getting publicity for your 'cast.

The book's first Chapter is the only one specifically for podcast listeners. It talks about sites and directories for finding the podcasts that are of interest to you. It also describes systems for downloading them, and the software for listening. Although the chapter contains much good info, it seems a bit out of place to me, in a book which is mostly of interest to people already looking to produce podcasts.

Chapters 2, 3 and 4 are "Starting Out", "Quality Sound", and "Formats". They dive into the gear and technology of recording and producing your podcasts.

Chapter 5 "Interviewing", and 7 "Publicity", tell about how to collect valuable and useful content, and how to get the word out to your potential audience.

Chapter 6 "Blogging" covers how to use a blog to publicize and distribute your podcast. It covers the most popular blogging systems like Movable Type, WordPress, Drupal and others. It covers using an existing blog, or setting up a new one. Also creating and managing the all-important RSS feed for your podcast. It also talks about internet hosting services which specialize in providing online storage and bandwidth for podcasts, which, because they are larger-sized files, can be a burden on traditional hosting arrangements.

Chapters 8 & 9, "Basic Editing" and "Advanced Audio", expand upon the post-production and audio tech material already covered. And Chapter 10 "On the Go" talks about recording podcasts out in the field.

"Podcasting Hacks" was first published in 2005, before the boom in video on the net, so it is short on info for video-podcasters. Though much of the discussion on interviewing, distribution, publicity, and hosting are directly applicable to video 'casts. Chapter 10 "Videoblogging" touches briefly on what was then an infant medium.

All in all, "Podcasting Hacks" a very useful and informative book, for both new and experienced podcasters.

Introduction
From the title, my impression was that this book would provide several specific technically-advanced strategies to maximize efficiency and enjoyment of podcasts. The strategies covered wouldn't necessarily be comprehensive, but rather serve as additional specialized tools one could add to the toolkit. Contrary to my impression, I was pleasantly surprised at the range of topics covered. I assumed from the term "hacks" in the title that the book's focus was going to be on adapting software and hardware for easier podcasting creation and consumption. However, there was plenty of focus on soft-skills as well, like methods of hacking your voice to sound better in a recorded format, or how to hack an experience you've had into a well-told and interesting story for a podcast.

Things I Liked

The book's foreward, believe it or not, contains the most succinct and accurate description of what podcasting is -- and isn't -- that I've read anywhere. I am mistrustful when a technology is advertised as "the hot new thing that everyone is doing!" because it usually seems to be a solution in search of a problem. That the foreward took a realistic tone made me favorably anticipate what would come in the rest of the book. The other thing that set this book apart was its range of contributors. There are hacks supplied by professional newscasters, popular podcasters, technologists of all stripes, and developers of podcasting tools and applications. These wide-ranging perspectives allowed the author to cover everything from writing Perl scripts to understanding basic copyright law to setting up a home studio to marketing your podcast - all in all, having this book is like getting to pick the brains of the top people doing podcasting, and having concise written documentation upon which to refer.

Things I Liked Not So Much

A minor point, but as someone who does not use Macs, PCs AND Linux boxes on a daily basis, I really only care about stuff available for the platform I work on. But the format of the book didn't allow me to easily locate the information relevant to me. When the book discussed software and hardware options, it wasn't clear which platform a hack was for until late into the description. A small addition to the hack title, like "Mac Only", would have remedied this.

In addition, the organization of the hacks was surprising and a little frustrating at times. For example,
Hack #2 is writing a perl script to re-assemble feeds of your choosing from other sites as a customized rebroadcast. As I was reading the hack, I thought about several questions one might be expected to have, such as "What is perl?", "What do I need to utilize this script?", and "How can I tell if this script will work with my web server"? These issues weren't covered until Hack #7. In another example, chapter 3 explores how to get quality sound; , the author uses terms like "condenser microphones" and "phantom power" early on, which he doesn't really explain until later on in the chapter when he discusses the various types of microphones.

Do you know how to listen to a podcast and produce one of your own? If you don't, this outstanding book is for you! Author Jack Herrington, has written a great book about how to find great podcasts and subscribe to them without filling your hard disk.

Herrington begins by showing you how to listen to podcasts through your browser and on a variety of different devices. Next, the author takes you through the basic hardware and software setup required to make high-quality podcasts. Then, he covers in depth how to pick the right audio hardware for your podcast; as well as, how to reduce noise to get that elusive clean sound. The author continues by covering the formats of various shows, and provides examples of formats; as well as, case studies of many popular podcasts. In addition, you'll also learn how to interview people, and how to edit the interviews. The author also concentrates on the mechanics of posting your podcasts to the Internet. Next, the author shows you how to market your podcast, make some money off it, and work with the podcasting community. Then, you will learn the basics of audio editing, what applications are available, and how to understand and use audio effects and filters. The author continues by taking things a step further and shows you how to build your own home studio, integrate audio feedback, add sound effects, and more. In addition, the author shows you how to take your show on the road with the hacks. Finally, he covers the basics of videoblogging and shows you how to create a teleprompter to give your videoblogs a professional feel.

So, if you want to get the best sound with the lowest noise, read this most excellent book. Herrington, has gone in great detail in this book, to help you produce a podcast that people will want to listen to, because of what you say and do.

As usual, Oreilly's combination of technical tips and tricks with straightforward implementation is excellent. I hadn't tried any of the Hacks series yet, and found that I'm thoroughly enjoying it. They are an excellent way to quickly get important pieces of information, while still comprehensively covering the topic.

The only downside is that it may not be a great book for those without some computer skills. But, if you know computers and don't know Podcasting, this is an excellent find.

Disclosure: my podcast is mentioned in his book. I find myself reaching for this book nearly every episode I create. I thought I was doing fine with my little show before Jack came out with this book. When it was published, I was shocked at how much he had gathered, and how much I had to learn! Jack has covered a very broad area, and yet kept a balance so that you feel like every page can be applied to your podcast. I find the guidance he gives on everything from equipment to environmental noise, to show format, to legal music use to be relevant to each episode I create. I continue to go back and find new tips to improve my show. I highly recommend it.

Mr. Bartle's writing is precise and his facts carefully researched, even the ones he experienced himself. This is a huge, superbly constructed history of the tools and philosophies developed over the years in experimental and commercial development of online virtual worlds. Because of Mr. Bartle's personal knowledge as a long-time designer and his sharp memory for the significance of trends and details, this book will raise anyone's appreciation of whatever virtual worlds one comes across on line or on disk, whether they be famous commercial ones or those developed by enthusiasts for their own pleasure. I would think it would be a must read for gaming students. What a grand, satisfying, fascinating book! And when one considers that this exciting history is only the beginning of VW development... Wow!

This book taught me the theory behind Virtual worlds and I beleive nearly everything I read in this book.

I didn't simply believe everything because it was a published book, I beleived it because Richard used examples from real games. With all the experiance Richard has you would expect him to have learnt everything the hard way, he has but he's also smart enough to realise that sometimes you can learn from others mistakes instead of making them yourself.

The book is aimed at the 'Dungeons and Dragons' (and most of his examples are) type of game but there is no reason the information cannot be used in other genres.

The most amusing part is how right he can be.
Richard states that 'you cannot allow players to carry items over from the Beta testing to the online game, even though your players will try to convince you otherwise'; something I didn't really think and didn't really agree with.
My family and I were all about to join 'Pirates of the Caribbean' when it started; when the announcement was made that players form the Beta test would be allowed to keep items my daughters asked what a Beta test was, I explained and now they don't want to play as they consider that to be cheating. We have all decided not to play.

Learn from others (like Richard) or pay the price.

James

Covers all the aspects of virtual worlds from a psycological perspective; the intentions, the types of virtual worlds.
Doesn't include indepth technology and the development issues related to designing virtual worlds
Good primer on virtual worlds.

To begin with, this book is not a programming book. There is no code, no discussion of VRML, MPEG-4, or X3D. Instead, this book stands back and takes a "big picture" look at the design of a virtual world from the viewpoint of systems engineering, social engineering, philosophy, history, and psychology. Ethical considerations are even tossed in for good measure.
The book starts out with chapters on the history of virtual worlds and the cultural influences that affected their characteristics. Next, there is a fly-over view of the "production line" of building a virtual world. Bartle then turns his attention to the players - who they are, what they want, and how a virtual world can meet their needs. World design is examined from the standpoint of virtual geography, virtual world citizens, and finally the physics required to implement your world. Chapter 5 is about the specific sociology and physiology of the virtual world - skill levels, individual characteristics, how virtual inhabitants divide themselves into groups, combat, and even the meaning of death in the virtual world. The final three chapters are very philisophical in nature. Chapter 6 is basically a liberal arts syllabus through the prism of virtual world design. The last chapter, on ethical considerations, talks about censorship, and also looks at the player as a person and how game playing in virtual worlds can hurt more than help some kinds of people, particularly those prone to addiction.
Bartle's social commentaries may be a bit long-winded for some people, although I found them interesting. Some readers may also be somewhat frustrated by the fact that the book talks more about what can go wrong in the design of a virtual world - overly complex and static story arcs, characters that players do not get invested in, characters in which players get too invested, etc - than what can go right. I really enjoyed the book, mainly because it moves the focus of the potential virtual world designer from the artistic and technical viewpoint to the player's viewpoint - why they plays games, and why a player would pick your game versus someone else's game.

You're getting it straight from the horse's mouth since this book is written by the grandfather of the modern MMORPG.
Rest assured - if you are a game designer, developer, or just love reading about game theory, this book is worth every penny.

I have read many other books on the subject and not one of them are packed with as much depth, knowledge, and wisdom. Bartle covers every avenue that a designer needs to consider in order to be successful. This book will help you and your team create an active, emergent virtual world.

As a game developer, I learned many valuable lessons on what made other games lose subscribers, or worse -- catastrophically fail.


Richard Bartle's writing style is very creative and detailed, and like his games, it gives you the 'just one more page' syndrome. For example, in this book it mentions how often a player must be rewarded in order to retain interest. He uses this same technique for writing by giving you something insightful to read atleast every 10 pages.


Bartle has covered all the bases. Designing Virtual Worlds is a great book, very entertaining. I give it 5 out of 5 stars - a must read.

More than 700 well-written pages packed with valuable insights, and it still leaves you begging for more.

Good instruction, a great price, and a growing-in-importance subject area all add up to a definite recommendation.

As a college student who spends hours and hours in front of a computer working on my thesis, this book has transformed the way I work. No longer do I suffer from back pain, sore wrists, and neck strain. Beautifully written, concise, and practical,"Ergaerobics" is truly a "must have" book for everyone! Every college campus should provide it for their students!

"Why does working @ my computer hurt so much" is the best book I've found on preventing repetitive stress injuries. It filled with practical information for anyone who spends long hours in front of a computer (secretaries, programmers, writers, college students).

The authors, both physical therapists, provide guidelines for arranging your workstation and how to sit there once it's arranged. The best part is an extensive list of exercises for your back,neck,jaw,thumbs,wrists,elbows, and shoulders designed specifically to prevent repetitive stress injuries. In addition, each exercise is illustrated so you never have to wonder if your doing the exercises correctly.

Once again, a great book!

As a college student who spends hours and hours in front of a computer working on my thesis, this book has transformed the way I work. No longer do I suffer from back pain, sore wrists, and neck strain. Beautifully written, concise, and practical,"Ergaerobics" is truly a "must have" book for everyone! Every college campus should provide it for their students!

ErgAerobics is a comprehensive guide to help computer users avoid "Computer Induced Repetitive Stress Injuries." In an easily understandable, entertaining, and concise manner ErgAerobics provides basic human anatomy information that anyone can understand as well as facts about Carpal Tunnel Syndrome, Lower Back Pain, Neck Pain, TMJ Disorder, Tennis Elbow, Shoulder Impingement Syndrome, Thoracic Outlet Syndrome, and DeQuervain's Disease. ErgAerobics offers tips on how to prevent and treat computer induced repetitive stress injuries, how to properly arrange a workstation, behavior modification techniques to help the reader interact with a computer in a safer, more cooperative manner. ErgAerobics is enhanced with simple, inconspicuous, effective exercises to help with the prevention and treatment of computer induced repetitive stress injuries including why, when, and how to exercise. If you spend days working at a computer - read ErgAerobics.

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.