So much writing about architecture tends to evaluate it on the basis of its intentions: how closely it corresponds to the artistic will of the designer, the technical skills of the builder, or whether it reflects the spirit of the place and time in which it was built, making it not much more than the willful (or even subconscious) assemblage of objects that result from design and construction techniques. Renowned writer and thinker David Leatherbarrow, in this groundbreaking new book, argues for a richer and more profound, but also simpler, way of thinking about architecture, namely on the basis of how it performs. Not simply how it functions, but how it acts, "its manner of existing in the world," including its effects on the observers and inhabitants of a building as well as on the landscape that situates it. In the process, Leatherbarrow transforms our way of discussing buildings from a passive technical or programmatic assessment to a highly active and engaged examination of the lives and performances, intended and otherwise, of buildings.

While most books on architecture concentrate on spatial themes, this book explores architecture's temporal dimensions. Through a series of close readings of buildings, both contemporary and classic, it demonstrates the centrality of time in modern architecture, and shows why an understanding of time is critical to understanding good architecture. All buildings exist in time. Even if designed for permanence, they change, slowly but inevitably. They change use, they accrue history and meaning, they decay – all of these processes are inscribed in time. So too is the path traced by the sun through a building, and the movements of the human body from room to room. Time, this book argues, is the framework for our spatial experience of architecture, and a key dimension of a building's structure and significance. Building Time presents twelve close readings of buildings and artworks which explore this idea. Examining works by distinctive modern architects – from Eileen Gray to Álvaro Siza and Wang Shu – it takes the reader, in some cases literally step-by-step, through a built work, and provides insightful reflections on the importance of 'making space for time' in architectural design. This is a book for both theorists and for architectural designers. Through it, theorists will find a way to rethink the fundamental premises and aims of design work, while designers will rediscover the order and ideas that shape the world around them-its buildings, interiors, and landscapes.

You can use this book to design a house for yourself with your family; you can use it to work with your neighbors to improve your town and neighborhood; you can use it to design an office, or a workshop, or a public building. And you can use it to guide you in the actual process of construction. After a ten-year silence, Christopher Alexander and his colleagues at the Center for Environmental Structure are now publishing a major statement in the form of three books which will, in their words, "lay the basis for an entirely new approach to architecture, building and planning, which will we hope replace existing ideas and practices entirely." The three books are The Timeless Way of Building, The Oregon Experiment, and this book, A Pattern Language. At the core of these books is the idea that people should design for themselves their own houses, streets, and communities. This idea may be radical (it implies a radical transformation of the architectural profession) but it comes simply from the observation that most of the wonderful places of the world were not made by architects but by the people. At the core of the books, too, is the point that in designing their environments people always rely on certain "languages," which, like the languages we speak, allow them to articulate and communicate an infinite variety of designs within a forma system which gives them coherence. This book provides a language of this kind. It will enable a person to make a design for almost any kind of building, or any part of the built environment. "Patterns," the units of this language, are answers to design problems (How high should a window sill be? How many stories should a building have? How much space in a neighborhood should be devoted to grass and trees?). More than 250 of the patterns in this pattern language are given: each consists of a problem statement, a discussion of the problem with an illustration, and a solution. As the authors say in their introduction, many of the patterns are archetypal, so deeply rooted in the nature of things that it seemly likely that they will be a part of human nature, and human action, as much in five hundred years as they are today.

What can you do with a degree in architecture? Where might it take you? What kind of challenges could you address? Architects After Architecture reframes architecture as a uniquely versatile way of acting on the world, far beyond that of designing buildings. In this volume, we meet forty practitioners through profiles, case studies, and interviews, who have used their architectural training in new and resourceful ways to tackle the climate crisis, work with refugees, advocate for diversity, start tech companies, become leading museum curators, tackle homelessness, draft public policy, become developers, design videogames, shape public discourse, and much more. Together, they describe a future of architecture that is diverse and engaged, expanding the limits of the discipline, and offering new paths forward in times of crisis. Whether you are an architecture student or a practicing architect considering a change, you’ll find this an encouraging and inspiring read. Please visit the Architects After Architecture website for more information, including future book launches and events: architectsafterarchitecture.com

Building software is harder than ever. As a developer, you not only have to chase ever-changing technological trends but also need to understand the business domains behind the software. This practical book provides you with a set of core patterns, principles, and practices for analyzing business domains, understanding business strategy, and, most importantly, aligning software design with its business needs. Author Vlad Khononov shows you how these practices lead to robust implementation of business logic and help to future-proof software design and architecture. You'll examine the relationship between domain-driven design (DDD) and other methodologies to ensure you make architectural decisions that meet business requirements. You'll also explore the real-life story of implementing DDD in a startup company. With this book, you'll learn how to: Analyze a company's business domain to learn how the system you're building fits its competitive strategy Use DDD's strategic and tactical tools to architect effective software solutions that address business needs Build a shared understanding of the business domains you encounter Decompose a system into bounded contexts Coordinate the work of multiple teams Gradually introduce DDD to brownfield projects

Provides information on analyzing, designing, and writing object-oriented software.