Computing Internet Books

Although the responsibility for user interface design should be delegated to experts, unfortunately as a programmer I have found myself on the "front line" doing user interface design. About Face is an excellent discussion of interface design issues for programmers. Cooper introduces a vocabulary for interface design that is beyond the specifics of precise button and label placement, etc.

For that reason, About Face is useful for any WIMP (Windows, Icons, Menus and Pointers) GUI system. The book's examples have a heavy Microsoft Windows and Office bias, however these are based on Windows 3.1 and Windows 95, so the Windows Forms designer should also be concentrating on the broader lessons of user interface design. You may even be able to successfully reinterpret these for designing Web forms.

First part has good touchs, second one is outdate!

I've long been curious about this book because it is so often cited and hailed by current usability experts as the "starting point of software usability." And maybe it was a groundbreaking work in 1995, when hardcore coders and "power users" still made up the majority of the user base. But now, many of Cooper's claims and proposals seem awkward or downright unusuable... the antithesis of what usability now stands for.

To be fair, this is an old book (in the IT sense of the word), and a new "About Face 2.0" is apparently hitting the shelves soon. Thank goodness! A lot of the ideas presented in the original are timeless and important, but others have hopefully been relegated to the dumpster.

Goal-directed design, for example, is something that interface designers should never lose sight of. Cooper does an excellent job of digging up the real goals of users (as distinct from their job descriptions) and maintaining focus on how to satisfy those goals while balancing them with other realistic business concerns-profit, professionalism, efficiency, and so forth. He decries the "real world analogy" trap that so many developers fall into and stresses the limits of "metaphors" in promoting user understanding. He stresses the importance of visual feedback for all actions and the need to protect users from "modes."

This is all good material that developers and project teams should always keep handy for the inevitable design arguments. (Although note that the tone of this book is relentlessly programmer-focused, hailing from a time when all "design" was done by coders, and interface or usability specialists simply didn't have a place in IT.)

But when Cooper gets into suggestions for "breaking the mold" and coming up with new and different types of interfaces, he loses me. He seems to vastly overestimate the readiness of users to learn new interface features and new designs. More recent comments from other usability sources acknowledge this basic truth. Joel Spolsky, for example, states that "An interface is well designed when it works exactly the way the user expects it would." Steve Krug states it even more baldly as "Don't make me think!" Don't make me think about the PROGRAM, that is; users are very willing to think about their tasks, they just refuse to waste time learning your cool new interface for what is (to them) just a complicated and badly-designed tool.

Cooper makes sweeping suggestions, such as doing away with file structures and directories entirely, or increasing the reliance on "chord clicking" and triple-clicking for key functions (for power users only, of course). He wants more icons and less text because of space considerations, even though he acknowledges that icons are inherently confusing to new users (idioms-something that can be learned only through experience) and are often poorly executed.

He also introduces several new concepts to the platform, such as a "milestones" feature in word processing. These new notions may perform valuable functions, but at what cost? Their suggested implmentation is awkward and confusing; the terms themselves are hard for non-coders to understand. Do we really want all dialog boxes to have an additional button: "OK, Cancel, Abandon"? It seems that, in his enthusiasm for trying something new and different, he temporarily forgets his own caveat: "No matter how cool your interface, less would be better."

I'm glad that a new version of this book has been developed; hopefully it has retained the core principles and jettisoned the specific examples, particularly the "totally new and different!" ideas. For better or worse, we have a standard for software interfaces now; changes must be approached with caution and delicacy, no matter how much of an improvement they seem to offer. Today's user base won't waste time learning a new interface and doesn't care how "cool" or even valuable it is. Don't forget the focus on user goals-and their goal will never be "learning to use this great new software."

This book is by no doubt a valuable resource for any software developer, nevertheless, more liveliness, humor or variety would have made it less monotonous. Prepare yourself to spend a great deal of time to tackle through more than half a thousand pages of very dense text, which is worth reading. The previous book by Alan Cooper, "The Inmates are Running the Asylum" is much more vivid, concise and amusing. I would recommend reading "The Inmates" first to get acquainted with Goal-Directed Design and the concept of considerate software, and then proceed to "About Face 2.0" to expand the knowledge and make it actionable.

This book exposes the distinction between implementation model and mental model, and brings the concept of "perpetual intermediates" as the most common category of the users. The authors show how to classify applications by posture on the web and on desktop and handheld computers, as well as on mobile phones and public kiosks.

The aspects of the modern User Interface are well covered in this book: data entry and retrieval, direct manipulation and pointing devices, metaphors, idioms and affordances. Parts of the book are devoted to such interface constituencies as controls, menus, toolbars and tooltips.

You will also find chapters about installation process and dialog etiquette in this book.

Cooper was bold enough to say "the program must inform the User when it (the software) gets stupid"...[and not the other way around]. Cooper exposes User Bashing error messages such as "invalid entry" and bogus warnings like "save changes before closing."

Cooper blows the lid on a dirth of best practices in the doldrums of corporate america (like a good Dilbert episode, only it's for real) : the ways software products (and their creators) make Users feel stupid, and in doing so how typical Micrsoft products fail to win friends and influence people (although they do sell boatloads of product). He picks on Microsoft and developers in general, not beause thery're evil, but because their "hurried to market" products cover thier own shortcomings and idiosyncrasies by blaming the User for their inability to perform.

While your waiting for this book to ship, just repeat the mantra "don't make Users feel stupid". This book pioneered the solution as a User Centered Design process, and the follow-on "Inmates Are Running the Asylum" is like a prequel establishing the need for this design methodology.

Book goes into too many details, but doesn't answer the simple question of: what parameters do I enter into the SARA transaction? What sequence do I apply to archive properly? Can archiving be used to carve out company data in a divestiture situation?

Though the initial chapters are bit redundant in data and little boring, if one can read the entire book with patience surely they will gain good intro and starting knowledge in Archiving.

It seems like so few people really understand this topic. I have been at a couple organizations that did not at all know what they were doing in terms of data archiving. This problem only gets worse over time... I found this book when it came out last year and I think anyone who needs to deal with archiving in SAP needs to read it. There are lots of easy steps that you can use right away. good luck.

Walters' comprehensive knowledge of the world of IT and incredible ability to explain complex concepts make this book a fascinating read for any gadget geek interested in how stuff actually works. And he doesn't settle for simple, surface level explanations. Instead of shying away from the details and tech-speak, Walters takes you one step further than you thought you could ever go through insightful examples and meaningful analogies.

In addition, his ability to put technological developments in context allow the reader to see the larger factors and trends that have and continue to drive change. A seemingly chaotic and overwhelmingly fast-changing industry suddenly seems logical and "trackable" after reading Walters' book. In this way, it's easy to forgive the fact that the text is a bit out of date. Everything I've read about today's technology I've easily been able to connect back to the ideas I learned here.

Truly one of a kind.

It is very cool book, I would say valuable book to build up your understanding of IT in general. It converges many technologies into one coherent pattern so you start to understand many things. I combined reading of this book with "UNIX Essentials" DVD and it nice to explore many of the conceptions in action. If you are lacking some evenness with your IT knowledge pick this one it is nicely shape your vision of it.

With 6+ years marketing management experience and an MBA, I feel this book was very helpful in understanding the many facets of technology and its evolution through time. The book is a must read for anyone who needs to build or brush up on a solid but basic understanding of technology. However, many of the newest trends in technology are only briefly covered. This is due, I believe, to the fact that many of the pervasive technologies and collaborative applications now being pushed in the marketplace didn't make the editor's draft of the book even though the published date is 2001.

There is a great breadth of information presented in a very lucid fashion. The material is easy to understand, and the author adds a great sense of humor.
However, with the rapid advancements in technology, the book is a bit dated. I would highly recommend this book to anyone who wants a gain a great breadth of knowledge in the field of Information technology, in a short period of time.

THE ESSENTIAL GUIDE TO COMPUTING is simply an extraordinary achievement. It reflects a breadth of knowledge and clarity of presentation that is remarkable. It makes every effort to distill knowledge about computers and computing in an easy, reader-friendly, memorable way. For computer users everywhere -- in organizations, schools, colleges and universities, and individuals -- this volume gives multiple ways of getting to know more about computing in its fast changing environment. First, you get to know the foundations of how computers and computing works in practical, everyday language. Second, you get a reference book that explains key terms, key workings, and key interconnections among the parts.

The most noteworthy aspect of the book is its superb coherence in presenting vast amounts of computing knowledge arranged in for easy understanding. Information and explanations in one chapter are referenced in subsequent ones, never failing to explain connections among them, with a view to present an overall picture of how computers and computing works.

Each chapter highlights technical terms related to computing and information technology, provides an overview of specific aspects as for example "An Overview of How Storage Works" (Chapter 2, p.40), and highlights in grey explanations of widely used terms such as "Disks From a User's Perspective" (p. 56). Each chapter also ends with a summary list of questions that focus on self-evaluating one's grasp of the chapter's contents.

E. Garrison Walters' book will continue to enrich the understanding of all who enjoy working with computers at work or for pleasure. I wish this book had been available to guide me in computing long before I found it, and, that I had written it ! It is a remarkable achievement!

This book covers a lot about Linux and has some great information to help someone study for the Linux+ exam. As others have noticed, I too have found a few typos. The book clearly wants to cover a lot of critical information about Linux and the exam, so certain sections are definitely lighter than others. I have not viewed the included CD yet, so cannot comment on its quality. If someone is looking to learn about Linux and is looking for a study guide for the Linux+ exam, this is a good start. I would caution readers who are also looking to use this book as a Linux reference book.

Robb Tracy does an excellent -- and up-to-date -- job of covering lots of Linux real estate. Whether you're a beginner or someone with experience, this book is worth the money. Between its extensive exercises, lab tests, drills, and self-tests, you will know this subject! Tracy also makes each chapter digestible, i.e., there are no endless chapters that wander. Those who failed their tests did so because they made the rookie mistake of relying on one resource. Jeez, read a second book dudes!

Bought this book because it had a high content (1000+ pgs), practice exams, and a test CD. Halfway through the book and I am already purchasing another Linux+ study guide because this one is flawed. Several practice exam questions do not match the given answers, there are *many* typos, alot of focus on general knowledge and not enough in depth review on probable exam topics per chapter.

I went with this book because it was the latest Linux+ study guide published, however I am going to purchase the Linux+ Study guide from Sybex as I had previously with my A+/Network+/Inet+ exams.

Do not let the large volume of this book fool you, alot of it is composed of basic knowledge which prepares you for the exam content. This book seems to be more orientated to the Beginner level user, one who has never touched Linux. If you are a intermediate-experienced Linux user, this book is not for you. If you are a beginner, I would definitely recommend getting a supplementary study guide to this book.

I've gone through 3 chapters of this book, and will be switching to a different one. There are enough errors both in the text and in the practice questions that I find it hard to trust what I read.

This book is a fairly good introduction to the principles of Linux system administration. Someone with little or no Linux experience should be able to use this book and learn quite a lot on the subject. There are numerous examples, and the practical labs included are good as well.

However, here are two serious caveats:

1. This book did not prepare me adequately for the actual CompTIA Linux+ certification exam. When I took the exam, I found questions on the exam covering concepts that were either not covered in this book, or were covered very briefly. The test is much more detailed and in-depth than this book goes, so I do not recommend that someone taking the Linux+ test rely solely on this book as a study aid for the test.

2. The book is filled with errors. They are mainly typographical errors, but there are a few errors where the author has simply misstated some of the information. I sent a 3-page errata sheet to the publisher. Hopefully they will publish an errata page for this book -- if so, it will be on the following Web page: http://www.mhprofessional.com/?page=/mhp/categories/computing/content/errata.html. You should check the site from time to time to see if they have published an errata sheet for this volume. Absent the errata sheet, keep your eyes open for numerous errors (file names spelled wrong, commands misprinted, etc.), especially in the self-test sections.

Overall, it is a book worth reading to learn about Linux, but due to the errors and due to the fact that it does not adequately meet its stated purpose as a Linux+ certification test prep guide, I gave it only 3 stars.

Okay, so I'm being grammatically incorrect.

Every day, somewhere, sand boxes and finger paints are being replaced in kindergartens and day care centers by flat panel displays and mice -- at taxpayer expense.

10 years later I'm still chewing over Cliff's consideration of the moral differences habituated in children by computer games, on the one hand, and kick-the-can on the other. The book is worth reading for this alone.

hiho

This book and author are such a joke it even showed up on Fark today! HILARIOUS!!! ex. He talks about how his local mall does more business in an afternoon than the ENTIRE INTERNET does in a MONTH!!!! I didn't read the book (only an excerpt he wrote) but this gem is like something from a time capsule predicting the future, but hilariously he predicts the exact OPPOSITE of everything that has come to be from 1995 to 2008! Yep, the Internet sure was just a big fad!

Hey Old Man River, watch your hip and good luck getting those dang kids off your lawn!

Paranoia over the internet and sadly his foresight was very limited. It's surprising that any educated person would predict the things he did.

I feel a little bit guilty in writing a review for a book about computing that is now several years old. As other reviewers have noted, there's a lot about this book that is horrendously dated: e-commerce is well-established, network access speeds have long since shattered 9600 baud, Usenet is (for all intents and purposes) dead.

But move beyond that for a minute. Ignore anything he says about download speeds (although you should consider that, according to the Pew Internet Project, only 42% of Americans have high-speed Internet access at home, so broadband isn't as ubiquituous as some would like us to believe). Smile when he questions the concept of e-commerce. Every time he references Usenet or newsgroups, mentally substitute blogs and web forums; do the same substition with MUDs and World of Warcraft.

Even now, 12 years after the fact, the questions that he raises are still important and relevant. While I can find fantastic recipes for bread online, it doesn't actually tell me anything about that instant when you know you've kneaded the bread long enough. Getting driving directions online is great, until you realise that construction or an accident is blocking your intended route and you can't figure out how to get around it because you don't have an actual paper map. Kids learning how to use computers is great, but when they can't do basic arithmetic or write a five-paragraph essay, how can we justify spending millions every year on computers in the classroom?

For all that I think that the questions that he raised need meaningful answers, I found the book unsatisfying. Stoll is obviously a computer geek himself, and was a heavy computer and Internet user at the time that he wrote the book, so it is frustrating that he offers up so much criticism without tempering it with some statements about what he does find useful online. The book reads like a conversation, which is somewhat annoying because it wanders all over the place and gets a bit repetitive. It could have been tightened up into a highly-compelling work.

Granted, this book is 12 years old, so it's going to be outdated. But many of Stoll's predictions and insights about the internet simply never came to pass. For instance, he claims that "few aspects of daily life require computers... they're irrelevant to cooking, driving, visiting, negotiating, eating, hiking, dancing, speaking, and gossiping." Not true. I've gotten countless wonderful recipes online, I wouldn't think of planning a trip without consulting an online map site, and I've learned more about different hiking trails via conservation websites than I would have ever come across in books or magazines. I understand that computers are not an absolute necessity. But I don't know what I would do without quick, easy, and inexpensive access to the information available on the internet these days. And that's saying nothing of e-commerce, which has revolutionized the trade of goods in this country over the last decade or so. Sorry, Cliff, but you were way off on this one.

Lammle does an excellent job of explaining complex networking concepts (particularly subnetting) in terms simple enough for someone with no previous exposure to networking to understand.

Unfortunately, some subjects were oversimplified, to the point that I felt underprepared for the CCNA test. If you are an excellent student, or you retain 100% of what you read, this book will get you a passing score on the exam. For the rest of us, I recommend Wendell Odom's CCNA Self Study Certification Library (Cisco Press - ISBN 1-58720-095-3). There's more to read, but you'll enter the exam more confident and better prepared.

-sean henning

The most challenging thing a certification test-prep book faces is the way it invariably will be misused. There is an old saw about using the right tool for the job, which in essence tells us to use the correct planning, strategy, and action to get the result we want. The majority of people purchasing a book like this are planning to take the CCNA exam and want some help preparing. This makes sense, and this is why I myself purchased Lamle's book. While it worked, and I passed with a 901, I couldn't help but wonder how much more difficult it would have been without hands-on experience with the devices, protocols and processes themselves at work. I have not yet met anyone who studied for, and passed, the CCNA test without any prior hands-on network experience.

It makes me very nervous to read someone's review suggesting, "This is the only preparation you need". To pass the test, you will likely need some experience as well, and to avoid the Catch-22 of requiring experience to get the job, yet also the job to gain the experience, I would recommend seeking first a junior position in the field, where you can not only get the experience, but also the mentoring of senior networking staff.

However, once you pass the test and have the cert, we face another challenge: "Does the cert verify your ability to apply what you know?" Not really, but that's why you cannot stop learning and developing your skills set there. You will likely need the CCNA to get the interview for the Networking job you seek, but you will need interview skills to get the job, and you will need to be able to APPLY your technical knowledge to keep it. Lamle's book is one of the best prep books out there for the CCNA. But if you plan to have a long-term career in Networking, do not think for a moment that you can stop there. And I'm not just talking about the next level of Cisco Certification.

Buy this book and study it, but make sure you maintain a long-term professional skills development plan, and if you don't already have it, start building your experience in the field. You'll need it.

Good luck!

I studied and passed my CCNA with this book in first try, it covers thoroughly on all you need to know about the exam. The bonus questions are useful too, few of them are pretty similiar to my exam questions.

This book definitely helped me pass my CCNA. The material in this book will definitely provide you with the tools you need in order to configure Cisco equipment and pass the CCNA the first time.

I passed the exam with a 901 the first try.

Wow, what a great author Todd is. His explainations and descriptions make the book well worth the cost. I used it as a text book for 2 classes and the last 3 out of 4 semesters for the Cisco Networking Academy. I also used his study guide (sold seperately but worth the money).
I not only learned what I needed feel confident about taking the CCNA, I feel very confident about my abilities with Cisco Networking Appliances. Todd should write for Cisco in my opinion.
I do feel that there are some easier ways to subnet than in his examples, but I learned it his way and then my instructors way. I chose what worked for me, your experiences will be different. Ultimately I used the Cisco Networking Academy, this book, and the study guide. I really studied hard, taking good notes and I passed the CCNA the first time with flying colors. I think Todd's explainations were key to this. He really makes Frame and ISDN configuation and the technolgies clear, he makes RIP and IGRP understandable even though they were the first IGPs that I was introduced to (they are very obscure IMO and I have never seen them used in the real world). I will look forward to his next version for the upgraded CCNA exams, I am sure they will be great.

Having been involved in web design and teaching the web fundamentals I was certainly surprised to see Cisco Press release a book dealing with web design. I was not surprise by how well detailed the book is since I have come to expect excellence from Cisco Press.

The authors put together a 660 page guide to help out even the most advanced web professional. From the start with the creation of the website using different protocols, connection types, browsers and services to web page elements and the decision of what goes into the web page itself this book seems fairly complete.

The authors also include other web design techniques using XHTML and CSS as well as setting up links, navigation, interactive pages, web hosting and marketing. After reading this book I found to very helpful in projects I am currently working on.

On the flip side the book does need more step by step instructions an how to perform some of the more key concepts and more hands on exercises. Also a cd should be included with practice files and exercises, however it does have several useful web tools and plenty of reference material

I haven't finished reading the book yet, but it seems to be well laid out.

First of all, having all the built-in documentation that comes with Powershell taking up the last 100 pages of the book is was basically useless. It just takes up valuable space on my bookshelf.

I have used the book a basic reference from time to time and it gives me the quick and dirty answer on how to do the basic stuff.

To really dig in deep I would suggest Bruce Payette's book, Powershell in Action. Who better to write a book than the author of the language itself!

If you are not an expert in scripting languages get this book immediately and in a week you will know 100 times more than today about PowerShell. If you are a scripting geek, then go directly to "PowerShell in Action".

Metaphorically speaking this book is cooked by a very good cook who was in a hurry. But the food is basically good and will give you a lot of energy.

And don't get too emotional, too 'religious' about it like a lot of people do! It is about your profession and fun - nothinng else!

Overall, I'm glad to have read this book. It isn't without it's problems, however, so let me get those out of the way first:

- The typesetting is poor. This definitely seems like a low-budget self-published book. Poor layout -- look for the proliferation of "example:" being followed by nearly a half page of whitespace. There are no chapter indications on the page headers, making it harder to find chapters without tediously looking for the page number on the Table of Contents.

- The binding seems like it might give out on me. So far it has held up, but I have the feeling that pages are going to start breaking out and flying off.

- Editing? What editing? One chapter stops short only to be tagged on at the end of a following chapter. There's other signs of self-editing mishaps, typos, etc.

- 149 pages of documentation which is no more useful than PowerShell's own help files. Or if you want gui documentation, PowerShell Analyzer has contextual help or you can use Sapien's PowerShell Help gui.

- Retails for $49.99. That's pretty steep for the quantity of material and the production quality. Other PowerShell books may retail for near that price-point, but Amazon is able to offer a discount to their customers.

- Finally, Mr. Jones likes to plug PrimalScript whenever possible. He mentions it from time to time in the book and in the webcasts he does for Microsoft. It's a fine product, though not my choice. (I prefer jEdit, gvim or emacs whenever possible; Karl Prosser's PowerShell Analyzer is great when working at depth specifically with PowerShell.)

But what about the content?

I found TFM to be very accessible. This book got me up and running with Powershell, and it did it without boring me with mind numbing hand-holding or putting me to sleep with over-my-head theory. Probably like a lot of other admin/support staff folks, I am not a programmer and don't have fluency in any particular language, though I *have* been exposed to the basics of a lot of different scripting languages and can put a script together from time to time. For my needs TFM hit the right balance as an introduction. I'm nearly finished with it, and will continue with Payette's book, which goes into greater detail. They're complimentary books, really.

Overall, I do appreciate this book. The production qualities need improving, but that doesn't derail the book from it's purpose. It serves as a good introduction to PowerShell aimed at the sysadmin crew.

UPDATE (20070320): I'm 168 pages into Bruce Payette's Windows PowerShell In Action and have to admit that it is a much more useful and successful book. It goes into significantly more detail about the hows and whys of PowerShell, and looks to be a book that I'll come back to again and again. I can't say the same about TFM, unfortunately. But it got me going, and for that I'll applaud it.

I'll agree with the previous reviewer on a couple of points:
1. They general layout of the book kind of hit me as odd when I first opened up the book.
2. The verboseness used to list out the packaged cmdlets doesn't seem like a good use for a book of this level.

I do have a lot of respect for Don and Jeff, and they provide a lot of support to the community.

I am just too busy right now to read from front to back, but have skimmed through some sections, and do like it. The book's binding was a bit stiff, but is starting to soften up a bit.

The formatting might need time for me to get a bit used to, but overall, I still give the book a 4/5, and look forward to other SAPIEN books in the TFM series.

This book is not a really a beginner scripting book, and I can fully understand that the authors didn't explain what WMI is, if at all.

I'm happy with my purchase, and am looking forward to learning more from it.

A true beginner should maybe go with the "Absolute Beginner" book out on PowerShell.
[...]