What do you think?
Rate this book
Bringing design to software
Design of software has often taken place in isolation from the many lessons learned in the design of objects or non-computer processes. Continuing in the tradition of Donald Norman's highly influential Design of Everyday Things, this collection of essays provides essential inspiration for reflective software designers driven by practical concerns of what works, what doesn't--and why. Contains contributions by such insightful software engineers as David Liddle, Donald Norman, John Bennett, and Michael Schrage.
Paperback
Published January 1, 1991
6 people are currently reading
101 people want to read
Ratings & Reviews
Friends & Following
Create a free account to discover what your friends think of this book!
Community Reviews
Displaying 1 - 3 of 3 reviews
January 19, 2014
I just re-read parts of this book and was reminded that John Seely Brown and Paul Duguid's chapter on Simplicity (Keep It Simple, chapter 7) is worth the price of the whole book. You can read just this chapter on JSB's website. http://www.johnseelybrown.com/keeping...
The book isn't light reading. It has a formal, not quite academic tone, but is filled with real-world examples, metaphors and descriptions that put everything into context quickly. Of course is a bit dated now, yet it's fantastic to see how much of what still needs to be done to create useful tools was outlined clearly in this book. A must-read for anyone interested in software design or technology design in general.
The book isn't light reading. It has a formal, not quite academic tone, but is filled with real-world examples, metaphors and descriptions that put everything into context quickly. Of course is a bit dated now, yet it's fantastic to see how much of what still needs to be done to create useful tools was outlined clearly in this book. A must-read for anyone interested in software design or technology design in general.
April 1, 2023
don’t waste your time on this book. it is outdated and full of material that is now completely irrelevant. i cannot find any usefull idea in this book: either pages are covered with banalities or with ideas that are completely irrelevant to software development and just added to the book because they contained some words about “design”.
September 25, 2008
These days, many companies have a position called Software Architect, but when this book was written, in 1996, there was no such thing. This is a collection of essays on how to design software written people who were pioneers in the field. It's a very interesting book, if you're a software developer.
Displaying 1 - 3 of 3 reviews