An exploration of published and unpublished writings of Alison and Peter Smithson, considering them in the context of the debates and discourses of postwar architecture. The English architects Alison Smithson (1928–1993) and Peter Smithson (1923–2003) were ringleaders of the New Brutalism, active in CIAM and Team 10, and influential in English Pop Art. The Smithsons, who met as architecture students, built only a few buildings but wrote prolifically throughout their career, leaving a body of writings that consider issues in architecture and urbanism and also take up subjects that are “not quite architecture” (the name of a series of articles written by Alison Smithson for the Architects' Journal)—including fashion design, graphic communication, and children's tales. In this book, M. Christine Boyer explores the Smithsons' writings—books, articles, lectures, unpublished manuscripts, and private papers. She focuses on unpublished material, reading the letter, the scribbled note, the undelivered lecture, the scrapbook, the “magic box,” as words in the language of modern architectural history—especially that of postwar England, where the Smithsons and other architects were at the center of the richest possible range of cultural encounters. Boyer is “writing around” the Smithsons' work by considering the cultural contexts in which they formed and wrote about their ideas. Boyer explains that the Smithsons were intensely concerned with the responsibility of the architect to ensure the quality of place, to build with lyrical appropriateness. They reached back to the country landscapes of their childhood and, Boyer argues, mixed their brand of New Brutalism with the English Picturesque. The Smithsons saw architects as both inheritors and passers-on. Their writings offer juxtapositions and connections, resembling an association of interactive loops, ideas waiting to be transmuted into built form.

As the digital economy changes the rules of the game for enterprises, the role of software and IT architects is also transforming. Rather than focus on technical decisions alone, architects and senior technologists need to combine organizational and technical knowledge to effect change in their company’s structure and processes. To accomplish that, they need to connect the IT engine room to the penthouse, where the business strategy is defined. In this guide, author Gregor Hohpe shares real-world advice and hard-learned lessons from actual IT transformations. His anecdotes help architects, senior developers, and other IT professionals prepare for a more complex but rewarding role in the enterprise. This book is ideal for: Software architects and senior developers looking to shape the company’s technology direction or assist in an organizational transformation Enterprise architects and senior technologists searching for practical advice on how to navigate technical and organizational topics CTOs and senior technical architects who are devising an IT strategy that impacts the way the organization works IT managers who want to learn what’s worked and what hasn’t in large-scale transformation

SHORTLISTED FOR THE ALICE DAVIS HITCHCOCK AWARD 'Brilliant' ELAIN HARWOOD 'Part history, part aesthetic autobiography, wholly engaging and liable to convince those procrastinators sitting (uncomfortably) on the concrete fence' JONATHAN MEADES 'A learned and passionate book' SIMON BRADLEY, author of The Railways 'A compelling and evocative read, meticulously researched, and filled with insight and passion' KATE GOODWIN, Head of Architecture, Royal Academy of Arts _______________________________ The raw concrete buildings of the 1960s constitute the greatest flowering of architecture the world has ever seen. The biggest construction boom in history promoted unprecedented technological innovation and an explosion of competitive creativity amongst architects, engineers and concrete-workers. The Brutalist style was the result. Today, after several decades in the shadows, attitudes towards Brutalism are slowly changing, but it is a movement that is still overlooked, and grossly underrated. Raw Concrete overturns the perception of Brutalist buildings as the penny-pinching, utilitarian products of dutiful social concern. Instead it looks a little closer, uncovering the luxuriously skilled craft and daring engineering with which the best buildings of the 1960s came into being: magnificent architectural visions serving clients rich and poor, radical and conservative. Beginning in a tiny hermitage on the remote north Scottish coast, and ending up backstage at the National Theatre, Raw Concrete embarks on a wide-ranging journey through Britain over the past sixty years, stopping to examine how eight extraordinary buildings were made - from commission to construction - why they have been so vilified, and why they are beginning to be loved. In it, Barnabas Calder puts forward a powerful case: Brutalism is the best architecture there has ever been, and perhaps the best there ever will be.

PAUL GOLDBERGER ON THE AGE OF ARCHITECTURE The Guggenheim Museum Bilbao by Frank Gehry, the CCTV Headquarters by Rem Koolhaas, the Getty Center by Richard Meier, the Times Building by Renzo Piano: Pulitzer Prize–winning critic Paul Goldberger’s tenure atThe New Yorkerhas documented a captivating era in the world of architecture, one in which larger-than-life buildings, urban schemes, historic preservation battles, and personalities have commanded an international stage. Goldberger’s keen observations and sharp wit make him one of the most insightful and passionate architectural voices of our time. In this collection of fifty-seven essays, the critic Tracy Kidder called “America’s foremost interpreter of public architecture” ranges from Havana to Beijing, from Chicago to Las Vegas, dissecting everything from skyscrapers by Norman Foster and museums by Tadao Ando to airports, monuments, suburban shopping malls, and white-brick apartment houses. This is a comprehensive account of the best—and the worst—of the “age of architecture.” On Norman Foster: Norman Foster is the Mozart of modernism. He is nimble and prolific, and his buildings are marked by lightness and grace. He works very hard, but his designs don’t show the effort. He brings an air of unnerving aplomb to everything he creates—from skyscrapers to airports, research laboratories to art galleries, chairs to doorknobs. His ability to produce surprising work that doesn’t feel labored must drive his competitors crazy. On the Westin Hotel: The forty-five-story Westin is the most garish tall building that has gone up in New York in as long as I can remember. It is fascinating, if only because it makes Times Square vulgar in a whole new way, extending up into the sky. It is not easy, these days, to go beyond the bounds of taste. If the architects, the Miami-based firm Arquitectonica, had been trying to allude to bad taste, one could perhaps respect what they came up with. But they simply wanted, like most architects today, to entertain us. On Mies van der Rohe: Mies’s buildings look like the simplest things you could imagine, yet they are among the richest works of architecture ever created. Modern architecture was supposed to remake the world, and Mies was at the center of the revolution, but he was also a counterrevolutionary who designed beautiful things. His spare, minimalist objects are exquisite. He is the only modernist who created a language that ranks with the architectural languages of the past, and while this has sometimes been troubling for his reputation . . . his architectural forms become more astonishing as time goes on.

A unique, eye-opening guide to Rome, one of the world s most magnificent cities"

This is a practical guide for software developers, and different than other software architecture books. Here's why: It teaches risk-driven architecting. There is no need for meticulous designs when risks are small, nor any excuse for sloppy designs when risks threaten your success. This book describes a way to do just enough architecture. It avoids the one-size-fits-all process tar pit with advice on how to tune your design effort based on the risks you face. It democratizes architecture. This book seeks to make architecture relevant to all software developers. Developers need to understand how to use constraints as guiderails that ensure desired outcomes, and how seemingly small changes can affect a system's properties. It cultivates declarative knowledge. There is a difference between being able to hit a ball and knowing why you are able to hit it, what psychologists refer to as procedural knowledge versus declarative knowledge. This book will make you more aware of what you have been doing and provide names for the concepts. It emphasizes the engineering. This book focuses on the technical parts of software development and what developers do to ensure the system works not job titles or processes. It shows you how to build models and analyze architectures so that you can make principled design tradeoffs. It describes the techniques software designers use to reason about medium to large sized problems and points out where you can learn specialized techniques in more detail. It provides practical advice. Software design decisions influence the architecture and vice versa. The approach in this book embraces drill-down/pop-up behavior by describing models that have various levels of abstraction, from architecture to data structure design.

What are the ingredients of robust, elegant, flexible, and maintainable software architecture? Beautiful Architecture answers this question through a collection of intriguing essays from more than a dozen of today's leading software designers and architects. In each essay, contributors present a notable software architecture, and analyze what makes it innovative and ideal for its purpose. Some of the engineers in this book reveal how they developed a specific project, including decisions they faced and tradeoffs they made. Others take a step back to investigate how certain architectural aspects have influenced computing as a whole. With this book, you'll discover: How Facebook's architecture is the basis for a data-centric application ecosystem The effect of Xen's well-designed architecture on the way operating systems evolve How community processes within the KDE project help software architectures evolve from rough sketches to beautiful systems How creeping featurism has helped GNU Emacs gain unanticipated functionality The magic behind the Jikes RVM self-optimizable, self-hosting runtime Design choices and building blocks that made Tandem the choice platform in high-availability environments for over two decades Differences and similarities between object-oriented and functional architectural views How architectures can affect the software's evolution and the developers' engagement Go behind the scenes to learn what it takes to design elegant software architecture, and how it can shape the way you approach your own projects, with Beautiful Architecture.

Practical Software Architecture Solutions from the Legendary Robert C. Martin (“Uncle Bob”) By applying universal rules of software architecture, you can dramatically improve developer productivity throughout the life of any software system. Now, building upon the success of his best-selling books Clean Code and The Clean Coder, legendary software craftsman Robert C. Martin (“Uncle Bob”) reveals those rules and helps you apply them. Martin’s Clean Architecture doesn’t merely present options. Drawing on over a half-century of experience in software environments of every imaginable type, Martin tells you what choices to make and why they are critical to your success. As you’ve come to expect from Uncle Bob, this book is packed with direct, no-nonsense solutions for the real challenges you’ll face–the ones that will make or break your projects. Learn what software architects need to achieve–and core disciplines and practices for achieving it Master essential software design principles for addressing function, component separation, and data management See how programming paradigms impose discipline by restricting what developers can do Understand what’s critically important and what’s merely a “detail” Implement optimal, high-level structures for web, database, thick-client, console, and embedded applications Define appropriate boundaries and layers, and organize components and services See why designs and architectures go wrong, and how to prevent (or fix) these failures Clean Architecture is essential reading for every current or aspiring software architect, systems analyst, system designer, and software manager–and for every programmer who must execute someone else’s designs. Register your product for convenient access to downloads, updates, and/or corrections as they become available.

Architects imagine the planet: fifty speculative world-scale projects from Patrick Geddes, Alison and Peter Smithson, Kiyonori Kikutake, Juan Navarro Baldeweg, Luc Deleu, and others. The world's growing vulnerability to planet-sized risks invites action on a global scale. The World as an Architectural Project shows how for more than a century architects have imagined the future of the planet through world-scale projects. With fifty speculative projects by Patrick Geddes, Alison and Peter Smithson, Kiyonori Kikutake, Saverio Muratori, Takis Zenetos, Sergio Bernardes, Juan Navarro Baldeweg, Luc Deleu, and many others, documented in text and images, this ambitious and wide-ranging book is the first compilation of its kind. Interestingly, architects begin to address the world as a project long before the advent of contemporary globalism and its assorted anxieties. The Spanish urban theorist and entrepreneur Arturo Soria y Mata, for example, in 1882 envisions a system that connects the entire planet in a linear urban network. In 1927, Buckminster Fuller's “World Town Plan—4D Tower” proposes to solve global housing problems with mobile structures delivered and installed by a Zeppelin. And Joyce Hsiang and Bimal Mendis visualize the conditions of a worldwide “City of Seven Billion” in a 2015–2019 project. Rather than indulging the cliché of the megalomaniac architect, this volume presents a discipline reflecting on its own responsibilities.