Reading Lost Twin Cities feels like you've found that great uncle or aunt who can explain all the black and white family photos. This is a great example of the historian's art, a real case in which an author, by choosing a particular way to frame a set of information, calls a past world back to vivid life. It's a bittersweet pleasure to relive the life span of each historical building. Millet's approach is anecdotal, like that old relative's conversational voice.

Indirectly, this book also raises some natural questions about our country's urban development. The demise of the Twin Cities' streetcar system is particularly well described, for example. I could see a creative professor, teaching a lower level course on urban development, assigning this book as a text. (The same professor would also have students view "Chinatown.")

The book was also adapted for television by the local (Minneapolis and Saint Paul) public station. The program is quite entertaining, and catches the tone of the book pretty well.

Larry Millet has written a few Sherlock Holmes mysteries, largely as an excuse to present much of this same historical information in a livelier way. If you're considering which approach to take, stick to this. The mysteries are awful, extremely flat-footed and despiriting for an Arthur Conan Doyle fan; this is a wonderful book.

So far the best architectural book I've read, especially since I'm from the area of the subjects.

I have a newer version of this book, and I just wanted to say that it is a very, very interesting book. Even if you arn't originally from the Twin Cities this book is still very interesting to look at to see how things have changed over the years such as the cars, the billboards/advertisements, and the way people dressed. I think that this is definetly worth every cent, and I look forward for another edition to come out with different photos of streets in the Twin Cities.

This is not a bad introductory documentation book, but quite skimpy in the amount of information and examples it contains.
Not sure it is worth buying at that price. I bought it after reading the previous reviews - I think they overrated it!

After reading my colleague's comments I rushed out and purchased this book. I, too, am trained and certified in Information Mapping© and was impressed at how closely the approach in this book is aligned to that method. However, what I like most is the fact that this book can be used as guidance for a wider scope than just documenting software architectures because it shows how to organize your documentation requirements, develop clear documentation and manage the entire process from start to finish.

I also like the clearly articulated and illustrated advice about how to augment text with graphics, and how to select the views and associated graphics to document requirements, specifications and the finished architecture. An example of how this book goes beyond documenting just architectures is a project in which I was engaged two years ago. One of the major deliverables was a set of operations guides. While this is related to architecture with respect to how its used after it's in production, there were no books that fully described how to go about it in a coherent way. Using the advice and techniques in this book I could have greatly improved upon what I did produce. While I cannot change the past, you can be sure that I'll use this book to its fullest the next time I need to write ops guides, especially when it comes to showing component and connector views, and elements and relations.

If you do technical writing either professionally or as a part of your job get this book and keep it nearby. If you read and use the material you're ability to communicate will surely improve, and you'll be able to tailor your documentation to each segment of your audience (business and technical), as well as to clearly communicate information. You'll also learn much about managing the documentation process itself.

Since reading a fascinating document titled "CMU/SEI-2001-TN-010 - Documenting Software Architectures: Organization of Documentation Package" a year ago and discovering that the approximately 20-page document was the basis for a book I have patiently waited, and am delighted with how the book turned out.

First, this book stands out as one of the clearest descriptions of how to not only document architectures, but how to manage the documentation project. Second, this is not a dogmatic prescription for how to document, but instead gives a set of techniques and views that can be used singularly or in combination to produce documentation that meets the needs of all technical and business stakeholders.

When I read the brief predecessor to this book I liked the way different view types and styles were introduced, but was left to my own imagination and creativity to employ them based on scant descriptions. This book rectifies those gaps by providing comprehensive guidance on how to create each view type and when it's most appropriate for inclusion into the documentation project. I was also intrigued by the earlier document because it discussed 'information chunking', which is the basis for a technique in which I'm trained and certified called Information Mapping©. The book expands on the earlier work, and it turns out that the material is not only consistent with Information Mapping© at a high level, but also shares many core principles. To me this is another plus because it will introduce readers who have not benefited from formal Information Mapping© training to powerful and effective document design and development techniques.

Another strong point about this book is the attention paid to managing the documentation process - it's one thing to write clear documentation and quite another to manage a process where many writers contribute to the documentation. I also liked the illustration examples, which epitomize how to effectively portray technical detail, and the discussion of other methods of documenting architecture.

In my opinion this book should become the standard for developing and managing documentation. It belongs on the desk of every technical writer and on the bookshelf of every architect and designer. I waited a year for this book and it was well worth the wait.