- Series: Princeton Legacy Library (Book 177)
- Paperback: 202 pages
- Publisher: Princeton University Press (July 14, 2014)
- Language: English
- ISBN-10: 0691607885
- ISBN-13: 978-0691607887
- Product Dimensions: 6 x 0.5 x 9.5 inches
- Shipping Weight: 10.4 ounces (View shipping rates and policies)
- Average Customer Review: 8 customer reviews
- Amazon Best Sellers Rank: #5,183,840 in Books (See Top 100 in Books)
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Programming as if People Mattered: Friendly Programs, Software Engineering, and Other Noble Delusions (Princeton Legacy Library) Paperback – July 14, 2014
The Amazon Book Review
Author interviews, book reviews, editors' picks, and more. Read it now
Customers who bought this item also bought
"This book is very easy to read, and is so entertaining that it is hard to put down.... An excellent book, and a must-read for software professionals." (Choice)
"The book provides a stimulating read, with a fair sprinkling of controversial opinions from which intelligent readers . . . will draw their own conclusions."---J. Dodd, Information and Science Technology
"This book's great glory is the author's implicit, but pervasive, notion that the human interface extends through software; and that programs are just ways that people tell computers what they should be doing. . . . [A] book filled with points to think about well before you start coding menus or screens." (UnixWorld)
"A witty look at the foibles of software engineering, based on real examples. . . . This voice of experience offers a good dose of humility to arrogant young programmers." (American Mathematical Monthly)
There was a problem filtering reviews right now. Please try again later.
Whereas "The Design of Everyday Things" has been updated and refined, this book is stuck in 1991. Many of the insights of the book are excellent, but there's a lot of material that is simply no longer relevant. I can only recommend this book to people who are willing to look past the pedantic style, occasional irrelevancies, and evaluations of decade old technology. I'd recommend Alan Cooper's book The Inmates are Running the Asylum instead, though that has its own problems.
If you can look past the obvious defects, there's a lot here for readers interested in user interface design. It's all anecdotal, but it's squares well with other quantitative works.
If you got this far in the review, there's a lot in the book to reward you for looking past the obvious defects. The primary source for Borenstein is his work on Andrew, a large Carnegie-Mellon University project, which, for various reasons, was reduced to a footnote in the history of computing.
One of the most notable observations a reader will make of the book is that the more things change, the more they stay the same. Many topics are just as relevant today as they were in 1991. For instance, his discussions on standards still offer insight. Part one starts us off on the basic problems of user interface design, and the chasm between regular users and programmers. Cooper offers a similar analysis, though the tone here is a lot more constructive.
The title of part 2, "The Dark Night of the Soul: The State of the Art in UI design" is a misnomer -- its real focus is the various people involved in UI design, including the HCI folks, programmers, and "the men in suits." Those familiar with the players can skip it. Much of this ground is covered in other books. If you always wondered why you can't get the cool toys from the MIT Media Lab articles, this explains why. The analysis of programmers is similar to Cooper, but with much less inflammatory tone. You can get the analysis of the management role anywhere - though his comments on them in the next section are excellent.
Part three is the meat. Borenstein gives us the benefit of his experience, with his "10 Commandments of user interface design." These are most excellent, and worth the price of admission. There's a few that feel like he might have been grasping a bit to reach the requisite 10, but that's a minor quibble. Most of the advice here is still valid, and you can easily think of modern software that could have benefited from this commentary.
Part 4 is everything else. Mostly, it contains introductory primers on development techniques, usability study, and project planning. Oddly, there's a strong chapter on the fundamental flaws in computer science education (circa 1991) that will ring true for many educated in that period.
I would love to see an updated version of this book. Much of Borenstein's advice still holds true, and a second edition could bring this wisdom to the development community. In the meantime, use the advice of part 3, and program as if people matter.
The book is an interesting look back at history. It has the text from the GNU General Public License from February 1989 and a chapter entitled "Information Wants to be Free." It also show how very lost the computer industry was at that time with regard to computer usability.
There are some war stories here about the cryptic and often dangerous UNIX command line. There are also some rants against the computers of the time (PC MSDOS, Macintosh, etc.) made by folks who made something they thought was better but "weren't getting any respect."
After rereading it recently those few interesting stories were still there but the book's disorganized structure, lack of index, and pedantic style haven't aged well. Those interested in HCI are better advised to read anything by Donald Norman, or any of the other excellent books written recently on HCI or cognative psychology.
- how "great" waterfall is when you plan everything in advance. And even then recognizing a UI is not waterfall
- a computer book cost $30 in 1992
- In 1988 HCI was split between HCI and CHI as an acronym
- why people were against change in going from line editors to the next step
- the screenshots of old software to illustrate usability issues
- James Gossling worked on the original windows management system referenced in the book
There were also parts that were still relevant:
- usability studies and art vs tech
- users are like three year olds. if they all want a cookie, maybe you should give them a healthy lunch which is what they really need