Patterns of Software - Dreamsongs

particular speed, the airfoil started to oscillate wildly, and the bridge collapsed. ... The promise of object-oriented programming—and of programming lan- ...... direction to search, a function to test whether two items are the same, and whether ...
1MB Sizes 1 Downloads 110 Views
Patterns of Software Tales from the Software Community Richard P. Gabriel

New York Oxford OXFORD UNIVERSITY PRESS 1996

Oxford University Press Oxford New York Athens Auckland Bangkok Bogota Bombay Buenos Aires Calcutta Cape Town Dar es Salaam Delhi Florence Hong Kong Istanbul Karachi Kuala Lumpur Madras Madrid Melbourne Mexico City Nairobi Paris Singapore Taipei Tokyo Toronto and associated companies in Berlin Ibaden

Copyright  1996 by Richard P. Gabriel Published by Oxford University Press, Inc., 198 Madison Avenue, New York, New York, 10016-4314 Oxford is a registered trademark of Oxford University Press All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior permission of Oxford University Press. Library of Congress Cataloging-in-Publication Data Gabriel, Richard P. Patterns of software: tales from the software community. p. cm. Includes Bibliographical references ISBN 0-19-5100269-X 1. Computer software—Development. 2. Object-oriented programming (Computer science) I. Title. QA76.76.D47G33 1996 005. 1—dc 2095-41883

1345798642 Printed in the United States of America on acid-free paper

To Jo Lawless, who led me away from the lion

Midway on our life’s journey, I found myself In dark woods, the right road lost. To tell About those woods is hard—so tangled and rough And savage that thinking of it now, I feel the old fear stirring: death is hardly more bitter.



Foreword A year or two ago, I was astonished to get several letters from diff erent people in the computer science field, telling me that my name was a household word in the software engineering community: specifically in the field of object-oriented technology. I had never even heard of object-oriented programming, and I had absolutely no idea that computer scientists knew my work, or found it useful or interesting; all this was a revelation to me. It was a pleasant revelation, but one that I did not really grasp at first; nor did I think much about it. I assumed the people who wrote to me were exaggerating anyway, out of politeness. Then, one of these people, Marc Sewell from IBM in Atlanta, came to see me and told me much the same, to my face, in a discussion over coff ee. Naturally, I assumed he too was exaggerating. When I expressed my surprise and doubts about the depth of this “alexandrian patterns movement,” he told me that in any given issue of The Journal of Object-Oriented Programming, there was almost certain to be some mention of my name. To prove it the next day he came with the current issue of The Journal of Object-Oriented Programming. There was in it, an article by Richard Gabriel, the essay that appears in this book as the chapter entitled “The Bead Game, Rugs, and Beauty.” I sat down to read the article; and for the first time, became truly interested in this connection. What was fascinating to me, indeed quite astonishing, was that in his essay I found out that a computer scientist, not known to me, and whom I had never met, seemed to understand more about what I had done and was trying to do in my own field than my own colleagues who are architects. Indeed, a cool factual appraisal or summary of my lifelong struggle with the problems of what to do in the field of architecture, has rarely been written objectively in the architectural literature. Architects, many of them agonizingly tied to a field which does not work, are mentally and emotionally tied up in the problems of the discipline, are often shocked by what I have said (either because it makes

vi

/

FOREWORD

them angry or because it makes them ecstatic), and have therefore rarely given large-scale cool appraisals of what I have written. Principally, I think this is because what I have to say, once taken seriously, has such enormous basementshaking results for architecture