The principles of good design from one programmer to another
Having taught this material for a number of years, I've received pounds of books on programming data structures. Carrying these books, my arms have become quite long. A week ago, my bookshelf was ripped from the wall. This book fights this trend: it's brief and to the point. With 20 pages of reading a week, you can conquer this text in the shortest of NBA seasons.
It is accompanied by a full suite of 50+ classes ready to be used or torn apart. All are described in a readable manner. (There are, for example, some jokes, subtle references to literature, not-so-subtle Berkshire restaurant recommendations, and just a little social commentary.)
This book also ventures to make statements about data structure design that are rare in such texts --- I give the reader good reasons to want to think about why designs are good or bad, and how to make design decisions armed with a few basic principles. After having worked in the both in industry and in academe, I think it's important that authors provide good examples of design, fully tested and worked through carefully. The result, I think is a polished contribution to my community.
There are many good exercises, some with answers. My students will be pleased to know that my exams were distilled to provide problems that make you think. Studing these problems will make my exams and, in general, data struture design, just a little bit easier.
I asked the book be published in hardcover because I want the reader to feel comfortable holding onto this text as a manual of design when they use my data structures, or better yet, design their own. If you don't buy the book, at least get the software and use it with the book of your choice!
Enjoy, and please, review this book, or send me your comments! --- duane (email@example.com)
--This text refers to an out of print or unavailable edition of this title.