What is essential knowledge for architecture? This frequently posed question targets fundamental principles of design, those basic criteria and priorities through which disciplinary stability is ensured. Yet, insofar as relevance is a core value of architecture in both theory and practice, the contingent nature of the future guarantees that some forms of knowledge not presently considered essential will eventually become indispensable. With that condition in mind, (Non-) Essential Knowledge for (New) Architecture collects projects that envision possible futures for architecture through speculations about new disciplinary knowledge. Asking what specific methods, materials, or understandings—tools, ratios, formulas, properties, principles, guidelines, definitions, rules, practices, techniques, reference points, histories, and more—not presently considered essential to architecture could, or should, define its future, this new volume of 306090 serves as both a gauge of contemporary concerns and a manual for emergent theory and practice.

In this truly unique technical book, today's leading software architects present valuable principles on key development issues that go way beyond technology. More than four dozen architects -- including Neal Ford, Michael Nygard, and Bill de hOra -- offer advice for communicating with stakeholders, eliminating complexity, empowering developers, and many more practical lessons they've learned from years of experience. Among the 97 principles in this book, you'll find useful advice such as: Don't Put Your Resume Ahead of the Requirements (Nitin Borwankar) Chances Are, Your Biggest Problem Isn't Technical (Mark Ramm) Communication Is King; Clarity and Leadership, Its Humble Servants (Mark Richards) Simplicity Before Generality, Use Before Reuse (Kevlin Henney) For the End User, the Interface Is the System (Vinayak Hegde) It's Never Too Early to Think About Performance (Rebecca Parsons) To be successful as a software architect, you need to master both business and technology. This book tells you what top software architects think is important and how they approach a project. If you want to enhance your career, 97 Things Every Software Architect Should Know is essential reading.

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.

An investigation of mathematics as it was drawn, encoded, imagined, and interpreted by architects on the eve of digitization in the mid-twentieth century. In Formulations, Andrew Witt examines the visual, methodological, and cultural intersections between architecture and mathematics. The linkages Witt explores involve not the mystic transcendence of numbers invoked throughout architectural history, but rather architecture’s encounters with a range of calculational systems—techniques that architects inventively retooled for design. Witt offers a catalog of mid-twentieth-century practices of mathematical drawing and calculation in design that preceded and anticipated digitization as well as an account of the formal compendia that became a cultural currency shared between modern mathematicians and modern architects. Witt presents a series of extensively illustrated “biographies of method”—episodes that chart the myriad ways in which mathematics, particularly the mathematical notion of modeling and drawing, was spliced into the creative practice of design. These include early drawing machines that mechanized curvature; the incorporation of geometric maquettes—“theorems made flesh”—into the toolbox of design; the virtualization of buildings and landscapes through surveyed triangulation and photogrammetry; formal and functional topology; stereoscopic drawing; the economic implications of cubic matrices; and a strange synthesis of the technological, mineral, and biological: crystallographic design. Trained in both architecture and mathematics, Witt uses mathematics as a lens through which to understand the relationship between architecture and a much broader set of sciences and visual techniques. Through an intercultural exchange with other disciplines, he argues, architecture adapted not only the shapes and surfaces of mathematics but also its values and epistemic ideals.

Job titles like “Technical Architect” and “Chief Architect” nowadays abound in software industry, yet many people suspect that “architecture” is one of the most overused and least understood terms in professional software development. Gorton’s book tries to resolve this dilemma. It concisely describes the essential elements of knowledge and key skills required to be a software architect. The explanations encompass the essentials of architecture thinking, practices, and supporting technologies. They range from a general understanding of structure and quality attributes through technical issues like middleware components and service-oriented architectures to recent technologies like model-driven architecture, software product lines, aspect-oriented design, and the Semantic Web, which will presumably influence future software systems. This second edition contains new material covering enterprise architecture, agile development, enterprise service bus technologies, RESTful Web services, and a case study on how to use the MeDICi integration framework. All approaches are illustrated by an ongoing real-world example. So if you work as an architect or senior designer (or want to someday), or if you are a student in software engineering, here is a valuable and yet approachable knowledge source for you.

Michael Sorkin's iconic list is now in a handsome printed package, a perfect gift for any architect, student of architecture, or design-savvy urbanist. By turns poetic and humorous, practical and wise, this book is a joyful celebration of the craft of architecture. A posthumous book by critic, architect, urban theorist, and educator, Michael Sorkin (1948-2020), 250 Things An Architct Should Know is filled with details that architects love to obsess over, from the expected (golden ratio and the seismic code) to the unexpected (the heights of folly and the prismatic charms of Greek islands.)

A study of historic architectural styles of New Orleans homes. This presentation of nineteenth-century gouache and watercolor archival paintings from the New Orleans Notarial Archives offers a glimpse at what old, renovated, restored, and new buildings in New Orleans neighborhoods not only might look like, but how they should look. Including examples of each New Orleans house type, ranging from the French colonial plantation home to the Creole cottage, this volume offers historic plans for each house along with contemporary adaptive-use alternatives to suit modern needs. An architectural pattern book, educational tool, city planner’s handbook, and stunning visual presentation, this gorgeous resource is intended for all interested in historic preservation and architectural history as well as those wishing to build a modern home in an authentic New Orleans style. Praise for A Pattern Book of New Orleans Architecture “An enchanting waltz through the heart of the Crescent City choreographed by the doyenne of New Orleans’ preservationists. [Toledano] presents two centuries of colored renderings from the New Orleans Notarial Archives in a stunning visual portrait of the city’s built heritage, while architect Gate Pratt’s pattern book of new homes designed in authentic styles provides an indispensable resource for rebuilding efforts. This work is destined to become the quintessential bible for historians, preservationists, architects, and all those interested in the true story of the architectural traditions that have shaped the ‘real’ New Orleans.” —Russell Versaci, AIA, traditional architect and author of Creating a New Old House and Roots of Home “For architects, builders, and developers working in the Crescent City, Roulhac B. Toledano’s A Pattern Book of New Orleans Architecture reveals an extraordinary new design resource. Toledano describes in detail the evolution of the city and the building types that have given the city a character unique in the world. Modern floor plans designed by local architects for historic house types demonstrate that the traditional architectural patterns of New Orleans are as accommodating today as in the past. For local practitioners and visitors wishing to build in New Orleans, Toledano’s pattern book is essential for sensitive and thoughtful design in this most exotic and precious city.” —Paul Ostergaard, AIA, Urban Design Associates, Pittsburgh, Pennsylvania