Chapter 1. Origins of Software Architecture
We are most of us governed by epistemologies that we know to be wrong.
Gregory Bateson
The purpose of this book is to help you design systems well and to help you realize your designs in practice. This book is quite practical and intended to help you do your work better. We must begin theoretically and historically. This chapter is meant to introduce you to a new way of thinking about your role as a software architect that will inform both the rest of this text and the way in which you approach your projects moving forward.
Software’s Conceptual Origins
We shape our buildings, and thereafter they shape us.
Winston Churchill
FADE IN:
INT. A CONFERENCE HALL IN GARMISCH GERMANY, OCTOBER 1968 — DAY
The scene: The NATO Software Engineering Conference.
Fifty international computer professors and craftspeople assembled to determine the state of the industry in software. The use of the phrase software engineering in the conference name was deliberately chosen to be “provocative” because at the time the makers of software were considered so far from performing a scientific effort that calling themselves “engineers” would be bound to upset the established apple cart.
MCILROY
We undoubtedly get the short end of the stick in confrontations with hardware people because they are the industrialists and we are the crofters. (pause) The creation of software is backwards as an industry.
KOLENCE
Agreed. Programming management will continue to deserve ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access