Vous voulez voir cette page en français ? Cliquez ici.

Have one to sell? Sell yours here
Programming as If People Mattered: Friendly Programs, Software Engineering, and Other Noble...
 
See larger image
 

Programming as If People Mattered: Friendly Programs, Software Engineering, and Other Noble... [Paperback]

Nathaniel S. Borenstein
3.5 out of 5 stars  See all reviews (2 customer reviews)

Available from these sellers.


Formats

Amazon Price New from Used from
Hardcover --  
Paperback --  

Product Details


Product Description

Review

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.

Book Description

Through a set of lively anecdotes and essays, Borenstein traces the divergence between the fields of software engineering and user-central software design, and attempts to reconcile the needs of people in both camps. "A book filled with points to think about well before you start coding menus or screens."--UnixWorld.

Tag this product

 (What's this?)
Think of a tag as a keyword or label you consider is strongly related to this product.
Tags will help all customers organize and find favorite items.
Your tags: Add your first tag
 

 

Customer Reviews

2 Reviews
5 star:    (0)
4 star:
 (1)
3 star:
 (1)
2 star:    (0)
1 star:    (0)
 
 
 
 
 
Average Customer Review
3.5 out of 5 stars (2 customer reviews)
 
 
 
 
Share your thoughts with other customers:
Most helpful customer reviews

4.0 out of 5 stars Look past the examples for timeless principles, Aug 12 2002
By 
Alex Moffat (Austin, TX USA) - See all my reviews
This review is from: Programming as If People Mattered: Friendly Programs, Software Engineering, and Other Noble... (Paperback)
Some of the reviews seem hung up on the "dated" quality of the examples. I think you need to look past this to see the underlying principles. For example, there is a chapter called "The quest for the perfect line editor". The example given is the change from line editors like ed to full screen editors like vi. The underlying principle is difficulty people have in accepting change. Or, the following quote "It may help to think of the user community as being like a preschool full of screaming three-year-olds. One doesn't have to rush to respond every time one of them cries a little bit, as crying is entirely natural for young children. But if some of all of the children begin to wail frequently, something is probably wrong and an investigation is warranted. If what they're all crying is "I want a cookie," that doesn't necessarily mean you should give them all cookies, but you might consider making them a healthy lunch to meet the underlying real need." Excellent advice, and a universal principle, from a chapter called "Listen to your users, but ignore what they say".
Help other customers find the most helpful reviews 
Was this review helpful to you? Yes No


3.0 out of 5 stars Dated, but still some good insight, May 2 2002
By 
Rob Purser (Wayland, MA USA) - See all my reviews
This review is from: Programming as If People Mattered: Friendly Programs, Software Engineering, and Other Noble... (Paperback)
Once upon a time, "Programming as if People Mattered" might be mentioned in the same article as books like "The Design of Everyday Things." Alas, unlike wine, even excellent software design books do not age well.

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.

Help other customers find the most helpful reviews 
Was this review helpful to you? Yes No

Share your thoughts with other customers: Create your own review
Most Helpful Customer Reviews on Amazon.com (beta)
Amazon.com: 3.3 out of 5 stars (7 customer reviews)

9 of 9 people found the following review helpful
5.0 out of 5 stars politically incorrect and true, thus delightful, Jun 18 2000
By Pat LaVarre - Published on Amazon.com
This review is from: Programming as If People Mattered: Friendly Programs, Software Engineering, and Other Noble... (Paperback)
Inspiring. Guerrila tactics for programmers who want to care about people yet somehow still get paid to work. On the whole, politically incorrect and true, thus delightful. In places, a touch sour. On my web page at home, the most recent of the three great art-of-programming books I list.

I liked one chapter so much that I typed out a softcopy myself by hand: a copy to read whenever I like. I mean Chapter 20 "The Ivory Tower". That chapter says ... We should reinvent the university experience of programmers to make the experience useful to the programmer. To become the first to teach programming well, let's try applying the approaches used to teach similar disciplines like architecture, or even anthropology, art, and drama.


6 of 6 people found the following review helpful
3.0 out of 5 stars Dated, but still some good insight, May 2 2002
By Rob Purser - Published on Amazon.com
This review is from: Programming as If People Mattered: Friendly Programs, Software Engineering, and Other Noble... (Paperback)
Once upon a time, "Programming as if People Mattered" might be mentioned in the same article as books like "The Design of Everyday Things." Alas, unlike wine, even excellent software design books do not age well.

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.


3 of 3 people found the following review helpful
4.0 out of 5 stars Look past the examples for timeless principles, Aug 12 2002
By Alex Moffat - Published on Amazon.com
This review is from: Programming as If People Mattered: Friendly Programs, Software Engineering, and Other Noble... (Paperback)
Some of the reviews seem hung up on the "dated" quality of the examples. I think you need to look past this to see the underlying principles. For example, there is a chapter called "The quest for the perfect line editor". The example given is the change from line editors like ed to full screen editors like vi. The underlying principle is difficulty people have in accepting change. Or, the following quote "It may help to think of the user community as being like a preschool full of screaming three-year-olds. One doesn't have to rush to respond every time one of them cries a little bit, as crying is entirely natural for young children. But if some of all of the children begin to wail frequently, something is probably wrong and an investigation is warranted. If what they're all crying is "I want a cookie," that doesn't necessarily mean you should give them all cookies, but you might consider making them a healthy lunch to meet the underlying real need." Excellent advice, and a universal principle, from a chapter called "Listen to your users, but ignore what they say".
 Go to Amazon.com to see all 7 reviews  3.3 out of 5 stars 
 
 
Only search this product's reviews



Listmania!

Create a Listmania! list

Look for similar items by category


Look for similar items by subject


Feedback