Architectural Technology Quotes

A new, self-employed architect scientist is the one in all the world who may accelerate realization of a high-standard survival for all, as now completely practical within the scope of available technology.

Good design is a renaissance attitude that combines technology, cognitive science, human need, and beauty to produce something that the world didn’t know it was missing.” —PAOLA ANTONELLI, curator of architecture and design, Museum of Modern Art

For the first time in architectural history, we're approaching the resolution and complexity of the natural world by creating new technologies that will ultimately enable us to design a beam as if it were a branch or an HVAC and waste removal system as if it were a photosynthetic GI tract engineered to convert carbon into biofuel.

The nice thing about twitter is the architecture of visibility. Email is invisible unless you reach out to someone directly. With Twitter, anyone can follow you and this is one of the big changes that was really introduced by Flickr, was this wonderful idea that you can follow somebody without their permission. Recognizing that relationships are asymmetrical, unlike facebook where we have to acknowledge each other otherwise we can’t see each other.

When we're able to communicate in nature's language; when we're able to transcend the view that nature is a boundless entity; even transcending the building as the kernel of the architectural project; when we invite scientific inquiry and technological innovation, fusing atoms with bits and bits with genes - only then will the art of building enable new forms of interaction between humans and their environment. Only then will we be able to design, construct and evolve as equals.

Not architecture alone but all technology is, at certain stages, evidence of a collective dream.

The Hedonistic Imperative outlines how genetic engineering and nanotechnology will abolish suffering in all sentient life. This project is ambitious but technically feasible. It is also instrumentally rational and ethically mandatory. The metabolic pathways of pain and malaise evolved only because they once served the fitness of our genes. They will be replaced by a different sort of neural architecture. States of sublime well-being are destined to become the genetically pre-programmed norm of mental health. The world's last aversive experience will be a precisely dateable event.

It is good to recall that three centuries ago, around the year 1660, two of the greatest monuments of modern history were erected, one in the West and one in the East; St. Paul's Cathedral in London and the Taj Mahal in Agra. Between them, the two symbolize, perhaps better than words can describe, the comparative level of architectural technology, the comparative level of craftsmanship and the comparative level of affluence and sophistication the two cultures had attained at that epoch of history. But about the same time there was also created—and this time only in the West—a third monument, a monument still greater in its eventual import for humanity. This was Newton's Principia, published in 1687. Newton's work had no counterpart in the India of the Mughals.

The problem of architecture as I see it is the problem of all art – the elimination of the human element from the consideration of the form.

When we're able to communicate in nature's language; when we're able to transcend the view that nature is a boundless entity; even transcending the building as the kernel of the architectural project; when we invite scientific inquiry and technological innovation, fusing atoms with bits and bits with genes - only then will the art of building enable new forms of interaction between humans and their environment.

Medieval technology could raise marvels of architecture 200 feet in the air, it could conceive the mechanics of a loom capable of weaving patterned cloth, and of a gearshaft capable of harnessing the insubstantial air to turn a heavy millstone, but it failed to conceive the fore-and-aft rig and swinging boom capable of adapting sails to the direction of the wind. By such accident of the human mind, war, trade, and history are shaped.

And yet, unlearn we must, for technology relentlessly transforms the playing field, changing not just the answers but the questions as well.

A digital computer is essentially a huge army of clerks, equipped with rule books, pencil and paper, all stupid and entirely without initiative, but able to follow millions of precisely defined operations. The difficulty lies in handing over the rule book.

Lying there, I thought of my own culture, of the assembly of books in the library at Alexandria; of the deliberations of Darwin and Mendel in their respective gardens; of the architectural conception of the cathedral at Chartres; of Bach's cello suites, the philosophy of Schweitzer, the insights of Planck and Dirac. Have we come all this way, I wondered, only to be dismantled by our own technologies, to be betrayed by political connivance or the impersonal avarice of a corporation?

To speak in nature's language, we must prioritize bio-based structural materials; biopolymers. Biopolymers are natural polymers produced by the cells of living organisms. We're already utilizing them in products, pharma, and even in fashion. But to deploy them on the architectural scale, we need to invest in design and construction technologies that emulate their heirarchical properties by engineering real time chemical formation.

In our unconsciousness we take credit where no credit is due, oblivious to the real source of everything we pretend is ours—the sacred origin not just of religion but also of everything else, of science and technology, education and law, of medicine, logic, architecture, ordinary daily life, the cry of longing, the excruciating ache of the awakening love for wisdom.

In pursuing a ‘way,’ Japanese typically move beyond an interest in craftsmanship to a kind of sacred search for the ultimate.

A smart city is an intelligent town that provides enormous possibilities for human growth through art, culture, social, architectural, economic, political, environmental, and scientific flowering with the optimal mix of nature, technology, humanity, and arts.

The externalization of memory [via the use of external symbolic storage systems] has altered the actual memory architecture within which humans think, which is changing the role of biological memory, the way in which the human brain deploys its resources, and the form of modern culture.

thinking of software architecture as a standalone concept that can be designed in isolation and then implemented by any group of teams is fundamentally wrong.

In 1966, Derrida delivered a paper entitled “Structure Sign and Play in the Discourse of the Human Sciences” (which is a wonderful paper, right up there with the original DynamoDB paper and the Page Rank algorithm paper).

Even the God of the Old Testament, faced with the continual querulousness of the tribes of Israel, had occasionally to ignite a piece of desert shrub to awe his audience into reverence. Technology would be the Modernists' burning bush.

Where technology acquisition was once the province of the CIO, today it’s the practitioner leading that process, because by the time a CIO typically hears about a project today, a majority of the technology and architectural decisions have already been made.

Foundational design principles regarding aesthetics, symbolism and meaning of place were for the old-timer carpenter, simply routine. Unfortunately, these principles began to lose their footing in the late 1800s, when building practices shifted toward more commercial technologies.

The first tool of authoritarian regimes is always informational control—both in the gathering of information on the public through surveillance and the filtration of information to the public through owned media. In its early days, the Internet seemed to pose a challenge to authoritarian regimes, but with the advent of social media, we are watching the construction of architectures that fulfill the needs of every authoritarian regime: surveillance and information control. Authoritarian movements are possible only when the general public becomes habituated to—and numbed by—a new normal.

Indeed, the bold, almost primitive, architecture of the CN Tower may reveal a basic truth about Canadian political existence as a perfect ideological symbol of the “technological nationalism” which has always been the essence of the Canadian state, and, most certainly, the locus of the Canadian identity.

Walt Disney often spoke of architecture and technology as functioning in the form of a ‘weenie’ – as something that would beckon the customer to go inside a space or cause the customer to go in a particular direction in a theme park. The weenie acts as a ‘reward. If you have a corridor, at the end there has to be something to justify you going that distance.

Bitcoin represents a fundamental transformation of money. An invention that changes the oldest technology we have in civilization. That changes it radically and disruptively by changing the fundamental architecture into one where every participant is equal. Where transaction has no state or context other than obeying the consensus rules of the network that no one controls. Where your money is yours. You control it absolutely through the application of digital signatures, and no one can censor it, no one can seize it, no one can freeze it. No one can tell you what to do or what not to do with your money. It is a system of money that is simultaneously, absolutely transnational and borderless. We’ve never had a system of money like that.

To avert climate crises, it's important that humanity protects and restores natural carbon sinks, like forests and wetlands. But modern advancements in architecture, materials science, and construction give us the ability to make our modern cities into carbon sinks. We have the technologies, the knowledge, and the capabilities to make cities more valuable to the natural ecosystem than forests are.

When we think of an institution, we can usually see it as embodied in a building: the Vatican, the Pentagon, the Sorbonne, the Treasury, the Massachusetts Institute of Technology, the Kremlin, the Supreme Court. What we cannot see, until we become close students of the institution, are the ways in which power is maintained and transferred behind the walls and beneath the domes, the invisible understandings which guarantee that it shall reside in certain hands but not in others, that information shall be transmitted to this one but not to that one, the hidden collusions and connections with other institutions of which it is supposedly independent. When we think of the institution of motherhood, no symbolic architecture comes to mind, no visible embodiment of authority, power, or of potential or actual violence. Motherhood calls to mind the home, and we like to believe that the home is a private place. Perhaps we imagine row upon row of backyards, behind suburban or tenement houses, in each of which a woman hangs out the wash, or runs to pick up a tear-streaked two-year-old; or thousands of kitchens, in each of which children are being fed and sent off to school. Or we think of the house of our childhood, the woman who mothered us, or of ourselves. We do not think of the laws which determine how we got to these places, the penalties imposed on those of us who have tried to live our lives according to a different plan, the art which depicts us in an unnatural serenity or resignation, the medical establishment which has robbed so many women of the act of giving birth, the experts—almost all male—who have told us how, as mothers, we should behave and feel. We do not think of the Marxist intellectuals arguing as to whether we produce “surplus value” in a day of washing clothes, cooking food, and caring for children, or the psychoanalysts who are certain that the work of motherhood suits us by nature. We do not think of the power stolen from us and the power withheld from us, in the name of the institution of motherhood.

I want to live to get back to my own time. I still hang on to the faint chance that the rainbow will come back for me and take me down the line to tell my tale in what I have already started to think of as the future. I want to make my report. The news I’d like to bring you people up there in the world of the future is that these Ice Age folk don’t see themselves as primitive. They know, they absolutely know, that they’re the crown of creation. They have a language—two of them, in fact—they have history, they have music, they have poetry, they have technology, they have art, they have architecture. They have religion. They have laws. They have a way of life that has worked for thousands of years, that will go on working for thousands more. You may think it’s all grunts and war-clubs back here, but you’re wrong. I can make this world real to you, if I could only get back there to you.

There is a tendency to romanticize the abilities of the ancient Egyptians because they produced structures that were miraculous for their time and certainly would pose a serious challenge to ours. They were somehow immensely more talented with sticks and stones than modern researchers have been able to demonstrate using the same implements. When pondering the theories proffered by Egyptologists, one gets the impression that an ancient Egyptian quarry worker was like a maestro playing a complete symphony on a violin made of a cigar box and a stick and producing the quality of a Stradivarius. The argument is pleasing and poetic, but the trouble is that, metaphorically speaking, when modern scholars make a violin from a cigar box and a stick, its results are precisely what you would expect from a cigar box and a stick. So the question persists: From what instruments did the symphonic architecture of Egypt materialize?

Militant atheists seek to discredit religion based on a highly selective reading of history. There was a time not long ago—just a couple of centuries—when the Western world was saturated by religion. Militant atheists are quick to attribute many of the most unfortunate aspects of history to religion, yet rarely concede the immense debt that civilization owes to various monotheist religions, which created some of the world’s greatest literature, art, and architecture; led the movement to abolish slavery; and fostered the development of science and technology. One should not invalidate these achievements merely because they were developed for religious purposes. If much of science was originally a religious endeavor, does that mean science is not valuable? Is religiously motivated charity not genuine? Is art any less beautiful because it was created to express devotion to God? To regret religion is to regret our civilization and its achievements.

We have to start accounting for the three themes that define women's relationship with that world. The first of these themes is the female body - or, to be precise - its invisibility. Routinely forgetting to accommodate the female body in design - whether medical, technological or architectural - has led to a world that is less hospitable and more dangerous for women to navigate. It leads to us injuring ourselves in jobs and cars that weren't designed for our bodies. It leads us to dying from drugs that don't work. It has led to the creation of a world where women just don't fit very well. There is an irony in how the female body is apparently invisible when it comes to collecting data, because when it comes to the second trend that defines women's lives, the visibility of the female body is key. That tend is male sexual violence against women - how we don't measure it, don't design our world to account for it, and in so doing, allow it to limit women's liberty.

Paul Virilio and I, in our different ways, share an intense interest in the changes brought about by technological innovation, by cultural and social upheavals, by natural catastrophes like earthquakes and the social and architectural responses to them. I see these extreme cases as the avant-garde of a coming normality, one that we must engage creatively now, inventing new languages, rules and methods, if we are to preserve what is essential to our humanity, that is, compassion, reason, independence of thought and action.

It may well be that what we have hitherto understood as architecture, and what we are beginning to understand of technology, are incompatible disciplines. The architect who proposes to run with technology knows now that he will be in fast company, and that in order to keep up he may have to discard his whole cultural load, including the professional garments by which he is recognized as an architect. If, on the other hand, he decides not to do this, he may find that a technological culture has decided to go on without him.

And that is why I would propose that, in our teaching of the humanities, we should emphasize the enduring creations of the past. The schools should stay as far from contemporary works as possible. Because of the nature of the communications industry, our students have continuous access to the popular arts of their own times - its music, rhetoric, design, literature, architecture. Their knowledge of the form and content of these arts is by no means satisfactory. But their ignorance of the form and content of the art of the past is cavernous.

The age of centralized, command-and-control, extraction-resource-based energy sources (oil, gas, coal and nuclear) will not end because we run out of petroleum, natural gas, coal, or uranium. It will end because these energy sources, the business models they employ, and the products that sustain them will be disrupted by superior technologies, product architectures, and business models. Compelling new technologies such as solar, wind, electric vehicles, and autonomous (self-driving) cars will disrupt and sweep away the energy industry as we know it.

In the nineteenth century, a young woman named Ellen Richards, trained in chemistry and unable to work in her field, announced the foundation of a new science she called oekology, or the science of living. This was the discipline later called domestic science or home economics, involving the effort to professionalize and dignify the work of the housewife by drawing on science and technology.* A single Greek root, oekos, has wandered through changing conceptions of human living, as well as changing fashions in spelling, producing the contemporary fields of economics and ecology, which frequently seem to be at odds. It also offers the less well-known term ekistics, coined by the city planner Constantinos Doxiadis to refer to a science of human settlement that would include the architectural creation of human spaces, their social and economic integration, and their relationship with the natural environment. Each of these latter-day coinages represents an incomplete view, but together they represent a view that includes biology and architecture, kitchens and stock exchanges, the growth of meadows and children as well as the GNP.

DevOps requires potentially new cultural and management norms and changes in our technical practices and architecture. This requires a coalition that spans business leadership, Product Management, Development, QA, IT Operations, Information Security, and even Marketing, where many technology initiatives originate. When all these teams work together, we can create a safe system of work, enabling small teams to quickly and independently develop and validate code that can be safely deployed to customers. This results in maximizing developer productivity, organizational learning, high employee satisfaction, and the ability to win in the marketplace.

Humanity has changed profoundly, and the accumulation of constant novelties exalts a superficiality which pulls us in one direction. It becomes difficult to pause and recover depth in life. If architecture reflects the spirit of an age, our megastructures and drab apartment blocks express the spirit of globalized technology, where a constant flood of new products coexists with tedious monotony. “Nobody is suggesting a return to the Stone Age,” he wrote. “But we do need to slow down and look at reality in a different way, to appropriate the positive and sustainable progress which has been made, but also to recover the values and the great goals swept away by our unrestrained delusions of grandeur.

Modern architects and engineers are still trying to understand how the ancient Greeks were able to build the Parthenon in ten years when the restoration of the monument has continued for more than three decades and is still not complete. What they have learned and shared along this arduous path of rediscovery is that the Greeks were highly skilled at building visual compensations into their structures. Columns were crafted and positioned to compensate for how the eye interprets what it sees at a distance. Subtle variances in the surface of platforms, columns, and colonnades provide the appearance of geometric proportion, whereas if they had worked from the perspective of a flat datum surface, the brain would interpret the results as being slightly skewed.

Movies have more power than any other medium to define the world we believe we live in.  When I was in high school, my classmates said that we didn’t have a “real” high-school experience because it wasn’t like what we saw on TV.  Ironically, reality was less “real” than fiction.  Motion pictures define our cultural consciousness.  I personally can’t imagine how I would process the world if I hadn’t watched movies.  There are certain experiences, like drugs and crime, that we know mostly from movies.  How we imagine the past and the future is largely determined by the films we’ve seen. And in some cases, the futures we’ve seen on screen influence the development of real technology and architecture, so that our fiction sets the course along which our reality will develop. The

We like to think of ourselves as immune from influence or our cognitive biases, because we want to feel like we are in control, but industries like alcohol, tobacco, fast food, and gaming all know we are creatures that are subject to cognitive and emotional vulnerabilities. And tech has caught on to this with its research into “user experience,” “gamification,” “growth hacking,” and “engagement” by activating ludic loops and reinforcement schedules in the same way slot machines do. So far, this gamification has been contained to social media and digital platforms, but what will happen as we further integrate our lives with networked information architectures designed to exploit evolutionary flaws in our cognition? Do we really want to live in a “gamified” environment that engineers our obsessions and plays with our lives as if we are inside its game?

His correspondence with Marianne includes a lot of links to news reports. At the moment they’re both engrossed in the Edward Snowden story, Marianne because of her interest in the architecture of global surveillance, and Connell because of the fascinating personal drama. He reads all the speculation online, he watches the blurry footage from Sheremetyevo Airport. He and Marianne can only talk about it over email, using the same communication technologies they now know are under surveillance, and it feels at times like their relationship has been captured in a complex network of state power, that the network is a form of intelligence in itself, containing them both, and containing their feelings for one another. I feel like the NSA agent reading these emails has the wrong impression of us, Marianne wrote once. They probably don’t know about the time you didn’t invite me to the Debs.

Conceive a world-society developed materially far beyond the wildest dreams of America. Unlimited power, derived partly from the artificial disintegration of atoms, partly from the actual annihilation of matter through the union of electrons and protons to form radiation, completely abolished the whole grotesque burden of drudgery which hitherto had seemed the inescapable price of civilization, nay of life itself. The vast economic routine of the world-community was carried on by the mere touching of appropriate buttons. Transport, mining, manufacture, and even agriculture were performed in this manner. And indeed in most cases the systematic co-ordination of these activities was itself the work of self-regulating machinery. Thus, not only was there no longer need for any human beings to spend their lives in unskilled monotonous labour, but further, much that earlier races would have regarded as highly skilled though stereotyped work, was now carried on by machinery. Only the pioneering of industry, the endless exhilarating research, invention, design and reorganization, which is incurred by an ever-changing society, still engaged the minds of men and women. And though this work was of course immense, it could not occupy the whole attention of a great world-community. Thus very much of the energy of the race was free to occupy itself with other no less difficult and exacting matters, or to seek recreation in its many admirable sports and arts. Materially every individual was a multi-millionaire, in that he had at his beck and call a great diversity of powerful mechanisms; but also he was a penniless friar, for he had no vestige of economic control over any other human being. He could fly through the upper air to the ends of the earth in an hour, or hang idle among the clouds all day long. His flying machine was no cumbersome aeroplane, but either a wingless aerial boat, or a mere suit of overalls in which he could disport himself with the freedom of a bird. Not only in the air, but in the sea also, he was free. He could stroll about the ocean bed, or gambol with the deep-sea fishes. And for habitation he could make his home, as he willed, either in a shack in the wilderness or in one of the great pylons which dwarfed the architecture even of the American age. He could possess this huge palace in loneliness and fill it with his possessions, to be automatically cared for without human service; or he could join with others and create a hive of social life. All these amenities he took for granted as the savage takes for granted the air which he breathes. And because they were as universally available as air, no one craved them in excess, and no one grudged another the use of them.

Nowadays, whether we like it or not, we are stuck with one form or another of advanced technology and we have got to make it work safely and efficiently: this involves, among other things, the intelligent application of structural theory. However, man does not live by safety and efficiency alone, and we have to face the fact that, visually, the world is becoming an increasingly depressing place. It is not, perhaps, so much the occurrence of what might be described as 'active ugliness' as the prevalence of the dull and the commonplace. Far too seldom is the heart rejoiced or does one feel any better or happier for looking at the works of modern man. Yet most of the artefacts of the eighteenth century, even quite humble and trivial ones, seem to many of us to be at least pleasing and sometimes incomparably beautiful. To that extent people—all people—in the eighteenth century lived richer lives than most of us do today. This is reflected in the prices we pay nowadays for period houses and antiques. A society which was more creative and self-confident would not feel quite so strong a nostalgia for its great-grandfathers' buildings and household looks.

In typical DevOps transformations, as we progress from deployment lead times measured in months or quarters to lead times measured in minutes, the constraint usually follows this progression: Environment creation: We cannot achieve deployments on-demand if we always have to wait weeks or months for production or test environments. The countermeasure is to create environments that are on demand and completely self-serviced, so that they are always available when we need them. Code deployment: We cannot achieve deployments on demand if each of our production code deployments take weeks or months to perform (i.e., each deployment requires 1,300 manual, error-prone steps, involving up to three hundred engineers). The countermeasure is to automate our deployments as much as possible, with the goal of being completely automated so they can be done self-service by any developer. Test setup and run: We cannot achieve deployments on demand if every code deployment requires two weeks to set up our test environments and data sets, and another four weeks to manually execute all our regression tests. The countermeasure is to automate our tests so we can execute deployments safely and to parallelize them so the test rate can keep up with our code development rate. Overly tight architecture: We cannot achieve deployments on demand if overly tight architecture means that every time we want to make a code change we have to send our engineers to scores of committee meetings in order to get permission to make our changes. Our countermeasure is to create more loosely-coupled architecture so that changes can be made safely and with more autonomy, increasing developer productivity.

The granite complex inside the Great Pyramid, therefore, is poised ready to convert vibrations from the Earth into electricity. What is lacking is a sufficient amount of energy to drive the beams and activate the piezoelectric properties within them. The ancients, though, had anticipated the need for more energy than what would be collected only within the King's Chamber. They had determined that they needed to tap into the vibrations of the Earth over a larger area inside the pyramid and deliver that energy to the power center—the King's Chamber —thereby substantially increasing the amplitude of the oscillations of the granite. Modern concert halls are designed and built to interact with the instruments performing within. They are huge musical instruments in themselves. The Great Pyramid can be seen as a huge musical instrument with each element designed to enhance the performance of the other. While modern research into architectural acoustics might focus predominantly upon minimizing the reverberation effects of sound in enclosed spaces, there is reason to believe that the ancient pyramid builders were attempting to achieve the opposite. The Grand Gallery, which is considered to be an architectural masterpiece, is an enclosed space in which resonators were installed in the slots along the ledge that runs the length of the gallery. As the Earth's vibration flowed through the Great Pyramid, the resonators converted the vibrational energy to airborne sound. By design, the angles and surfaces of the Grand Gallery walls and ceiling caused reflection of the sound, and its focus into the King's Chamber. Although the King's Chamber also was responding to the energy flowing through the pyramid, much of the energy would flow past it. The specific design and utility of the Grand Gallery was to transfer the energy flowing through a large area of the pyramid into the resonant King's Chamber. This sound was then focused into the granite resonating cavity at sufficient amplitude to drive the granite ceiling beams to oscillation. These beams, in turn, compelled the beams above them to resonate in harmonic sympathy. Thus, with the input of sound and the maximization of resonance, the entire granite complex, in effect, became a vibrating mass of energy.

Discussions around architecture often focus on tools and technologies. Should the organization adopt microservices or serverless architectures? Should they use Kubernetes or Mesos? Which CI server, language, or framework should they standardize on? Our research shows that these are wrong questions to focus on. What tools or technologies you use is irrelevant if the people who must use them hate using them, or if they don’t achieve the outcomes and enable the behaviors we care about. What is important is enabling teams to make changes to their products or services without depending on other teams or systems. Architects should collaborate closely with their users—the engineers who build and operate the systems through which the organization achieves its mission—to help them achieve better outcomes and provide them the tools and technologies that will enable these outcomes.

Given our skills, constraints, cultural and engineering maturity, desired software architecture, and business goals, which team topology will help us deliver results faster and safer?

By 2006, they had created an international exemplar of interconnectedness. Estonian software engineers had not only created Skype; they were helping to build a new society, where the only rituals requiring you to show up in person and present a document were marriage, divorce, and buying property. Everything else was online—government, banking, finance, insurance, communications, broadcast and print media, the balloting for elections. Wi-Fi was strong, ever present, and free. People began to call their homeland e-Estonia. They had created the first country whose political and social architectures were framed by an internet infrastructure—and perhaps the most technologically sophisticated nation on earth. In April 2007, the authorities in Tallinn decided to move the Bronze Soldier from its pedestal to a military cemetery. Estonian patriots found it offensive, Russian nationalists came to Estonia to rally around it, and the statue became a flash point of confrontation. Russia’s foreign affairs minister, Sergey Lavrov, called the decision disgusting; he warned of serious consequences for Estonia. An angry mob of Russians ran riot in the capital. In Moscow, young thugs laid siege to the Estonian embassy and forced it to shut down. And then Putin waged political warfare in a way that made Estonia’s strength its weakness.

Natural materials express their age, as well as the story of their origins and their history of human use. All matter exists in the continuum of time; the patina of wear adds the enriching experience of time to the materials of construction […] Buildings of this technological era usually deliberately aim at ageless perfection, and they do not incorporate the dimension of time, or the unavoidable and mentally significant processes of aging. This fear of the traces of wear and age is related to our fear of death.

Buddhism first came to Korea during the fourth century a.d. Virtually from its inception on the peninsula, the religion was a principal force behind social and technological change in Korea. Along with their religion, Buddhist missionaries introduced to Korea a wide cross-section of Sinitic culture and thought, including the Chinese writing system, calendrics, and architecture. Buddhist spiritual technologies were also considered to offer powers far superior to those of the indigenous religion of Shamanism. For all these reasons, Buddhism became an integral part of the religio-political nexus of Korea during the Unified Silla (668-935) and Koryŏ (937-1392) dynasties. Buddhism therefore provided the foundation for Korean national ideology for over a millennium.

The development of an open format for a whole model is hardly relevant anymore, as long as you are able to move data around.

Architecture has a history of adopting tools that have been developed for other reasons. It’s not a driving force of innovation. It rarely has been.

anyone who makes decisions about the shape and placement of engineering teams is strongly influencing the software systems architecture.

organizing team structures to match the architecture they want the system to exhibit rather than expecting teams to follow a mandated architecture design.

there are significant advances on the horizon, such as the graphics-processor unit, which uses parallel computing to create massive increases in performance, not only for graphics, but also for neural networks, which constitute the architecture of the human brain.

A sea of faces, young, perspiring and eager, had been raised solemnly -for forty-five minutes—to the platform where Guy Francon had held forth as the speaker at the commencement exercises of the Stanton Institute of Technology, Guy Francon who had brought his own person from New York for the occasion; Guy Francon, of the illustrious firm of Francon & Heyer, vice-president of the Architects’ Guild of America, member of the American Academy of Arts and Letters, member of the National Fine Arts Commission, Secretary of the Arts and Crafts League of New York, chairman of the Society for Architectural Enlightenment of the U.S.A.; Guy Francon, knight of the Legion of Honor of France, decorated by the governments of Great Britain, Belgium, Monaco and Siam;

The value of business architecture is to provide an abstract representation of an enterprise and the business ecosystem in which it operates. By doing so, business architecture delivers value as an effective communication and analytical framework for translating strategy into actionable initiatives. The framework also enhances the enterprise’s capacity to enact transformational change, navigate complexity, reduce risk, make more informed decisions, align diverse stakeholders to a shared vision of the future, and leverage technology more effectively

If the architecture of the system and the architecture of the organization are at odds, the architecture of the organization wins.

This key architectural property enables teams to easily test and deploy individual components or services even as the organization and the number of systems it operates grow—that is, it allows organizations to increase their productivity as they scale.

Instead of choosing between a monolithic architecture or a microservices architecture, design the software to fit the maximum team cognitive load. Only then can we hope to achieve sustainable, safe, rapid software delivery. This team-first approach to software boundaries leads to favoring certain styles of software architecture, such as small, decoupled services.

there is no technology that can promise that any authorized software that wants to receive and interpret an event — or at least its metadata — can do so at will.

That’s because many of them had been secretaries—users of the equipment. These guys, maybe they punched a button on a copier one time in their lives, but they had someone else do their typing and their filing. So we were trying to sell to people who really had no concept of the work this equipment was actually accomplishing. “It didn’t register in my mind at that event, but that was the loudest and clearest signal we ever got of how much of a problem we were going to have getting Xerox to understand what we had.” There was at least one other harbinger of the coming letdown. Toward the end of the evening McColough, Kearns, and a few of the executive staff materialized in the demo room. Their appearance had been prearranged. “They were there to have an opportunity to say, ‘Well, now we’re going to do something, guys,’” Ellenby recalled. “But they didn’t take that opportunity. They just said, ‘Thank you.’ “I was expecting a bit more than that,” he said. “We’d developed a camaraderie that was quite unusual. My people felt pumped up and hyped, like a sporting team. Instead what we got was, ‘Thanks, boys, the war is over, and you can take your horses back.’” Thus did the doubts surface almost before the euphoria of a flawless demonstration had a chance to run its course. Despite McColough’s ringing re-endorsement of “the architecture of information,” his and Kearns’s equivocal farewell told Ellenby and his team that they were naïve to think Xerox would exploit this technology anytime soon. And in this beleaguered and distracted corporation, Ellenby knew, time was the enemy.

If the desired theoretical system architecture does not fit the organizational model, then one of the two will need to change.

For me, a real breakthrough occurred when I stopped thinking about and defining meat in terms of its animal origin (e.g., chicken, cow, pig), but instead in terms of its composition. At a very high level, meat is really five things: amino acids, lipids, small amounts of carbohydrates, trace minerals, and, of course, water. The animal eats plants and turns them into muscle tissue, or what we call meat. But with today’s technology, instead of using a biological bioreactor (animal), we can harvest those core inputs directly from plants themselves. We can use other systems to assemble them in the familiar architecture of meat.

In other words, the blueprint view has many functions, but they all relate to abstract and technological purposes (in this case, architectural purposes.) You in your daily life remain in the “perspectivist” position, and if you want to shift to the absolutist or blueprint position you must remember the purpose of doing this — e.g., solving a real problem in architecture, or just getting the thrill of a novel view of the room. If you forget the purpose, and think the absolutist view has all the truth and the only truth, you have mistaken the map for the territory. When I call this “crazy,” I do not think I exaggerate. The only form of Idolatry (symbol-worship) loonier than this which I can imagine would occur if you ate the menu instead of eating the meal.

These capabilities include (but are not restricted to): ​•​Application security ​•​Commercial and operational viability analysis ​•​Design and architecture ​•​Development and coding ​•​Infrastructure and operability ​•​Metrics and monitoring ​•​Product management and ownership ​•​Testing and quality assurance ​•​User experience (UX)

Node.js is a powerful, open-source, server-side JavaScript runtime environment that enables developers to build scalable and high-performance applications. Leveraging event-driven architecture and non-blocking I/O operations, Node.js allows for efficient handling of concurrent requests, making it ideal for building real-time web applications, APIs, and microservices. With its extensive ecosystem of libraries and frameworks, Node.js empowers developers to create fast, lightweight, and modern applications across various domains.

Despite the relentless effort to remove coordination and synchronization in core technologies, we have, for the most part, neglected organizational and architectural coordination. As a result, no matter how fast our computer systems run, achieving outcomes have fallen behind coordinating activities of teams and humans.

Andrew Gibbons charts our investigation with a comparison of the design activity in other professional fields such as architecture and digital design to instructional design. He maps the theories and practices of instructional design to the broader fields of design and examines the range of scales present in design practice. Building from the seminal work of Donald Schön in his examination of the architectural design studio, Monica Tracy and John Baaki examine the principle of Refection-in-Action in terms of theory, design practice, and our understanding of the design process, illuminating these examples through the lens of a case study of active designers. How instructional designers learn and evolve as practitioners is examined by Elizabeth Boling and

While many of the DevOps patterns shown in this book require automation, DevOps also requires cultural norms and an architecture that allows for the shared goals to be achieved throughout the IT value stream.

Neo-classicism, not just in architecture and urban planning but also in remaking archaeological sites and shaping culture in general, became the colonial technology which was transplanted from Munich, Berlin, and Paris,36 a technology that merged monumentalization with capitalist modernization.

The medievalist has the capacity, and the desire, to harmonize. He believes the planets sing in harmony; why cannot technology also sing?

No foreign architect of stature, such as I. M. Pei, resides in Japan. Foreign architects come to Japan on short-term contracts, erect a skyscraper or a museum, and then leave. But subtle and sophisticated approaches to services and design—the core elements of modern building technology—cannot be transmitted in this way. Japan is left with the empty shells of architectural ideas, the hardware without the software.

Technology is transforming nearly every sector of our lives. Music, books, retailing, communication, news, photography, medicine, architecture, etc. etc. etc. have changed drastically, have become more efficient, and we all expect that those changes, improvements, and progress will continue. Education cannot sit in this customized world as an island, embracing the Industrial Age, and expect to survive.

s s i o n o f R a t i o n a l S o f t w a r e C o r p o r a t i o n i s t o e n s u r e t h e s u c c e s s o f c u s t o m e r s c o n s t r u c t i n g t h e s o f t w a r e s y s t e m s t h a t t h e y d e p e n d o n . We enable our customers to achieve their business objectives by turning software into a source of competitive advantage, speeding time-to-market, reducing the risk of failure, and improving software quality. We fulfill our mission with the Rational ApproachTM, a comprehensive softwareengineering solution consisting of three elements: • A configurable set of processes and techniques for the development of software, based on iterative development, object modeling, and an architectural approach to software reuse. • An integrated family of application construction tools that automate the Rational Approach throughout the software lifecycle. • Technical consulting services delivered by our worldwide field organization of software engineers and technical sales professionals. Our customers include businesses in the Asia/Pacific region, Europe, and North America that are leaders in leveraging semiconductor, communications, and software technologies to achieve their business objectives. We serve customers in a diverse range of industries, such as telecommunications

o n o f R a t i o n a l S o f t w a r e C o r p o r a t i o n i s t o e n s u r e t h e s u c c e s s o f c u s t o m e r s c o n s t r u c t i n g t h e s o f t w a r e s y s t e m s t h a t t h e y d e p e n d o n . We enable our customers to achieve their business objectives by turning software into a source of competitive advantage, speeding time-to-market, reducing the risk of failure, and improving software quality. We fulfill our mission with the Rational ApproachTM, a comprehensive softwareengineering solution consisting of three elements: • A configurable set of processes and techniques for the development of software, based on iterative development, object modeling, and an architectural approach to software reuse. • An integrated family of application construction tools that automate the Rational Approach throughout the software lifecycle. • Technical consulting services delivered by our worldwide field organization of software engineers and technical sales professionals. Our customers include businesses in the Asia/Pacific region, Europe, and North America that are leaders in leveraging semiconductor, communications, and software technologies to achieve their business objectives. We serve customers in a diverse range of industries, such as telecommunications, banking and financial services, manufacturing, transportation, aerospace, and defense.They construct software applications for a wide range of platforms, from microprocessors embedded in telephone switching systems to enterprisewide information systems running on company-specific intranets. Rational Software Corporation is traded on the NASDAQ system under the symbol RATL.1

Education was still considered a privilege in England. At Oxford you took responsibility for your efforts and for your performance. No one coddled, and no one uproariously encouraged. British respect for the individual, both learner and teacher, reigned. If you wanted to learn, you applied yourself and did it. Grades were posted publicly by your name after exams. People failed regularly. These realities never ceased to bewilder those used to “democracy” without any of the responsibility. For me, however, my expectations were rattled in another way. I arrived anticipating to be snubbed by a culture of privilege, but when looked at from a British angle, I actually found North American students owned a far greater sense of entitlement when it came to a college education. I did not realize just how much expectations fetter—these “mind-forged manacles,”2 as Blake wrote. Oxford upholds something larger than self as a reference point, embedded in the deep respect for all that a community of learning entails. At my very first tutorial, for instance, an American student entered wearing a baseball cap on backward. The professor quietly asked him to remove it. The student froze, stunned. In the United States such a request would be fodder for a laundry list of wrongs done against the student, followed by threatening the teacher’s job and suing the university. But Oxford sits unruffled: if you don’t like it, you can simply leave. A handy formula since, of course, no one wants to leave. “No caps in my classroom,” the professor repeated, adding, “Men and women have died for your education.” Instead of being disgruntled, the student nodded thoughtfully as he removed his hat and joined us. With its expanses of beautiful architecture, quads (or walled lawns) spilling into lush gardens, mist rising from rivers, cows lowing in meadows, spires reaching high into skies, Oxford remained unapologetically absolute. And did I mention? Practically every college within the university has its own pub. Pubs, as I came to learn, represented far more for the Brits than merely a place where alcohol was served. They were important gathering places, overflowing with good conversation over comforting food: vital humming hubs of community in communication. So faced with a thousand-year-old institution, I learned to pick my battles. Rather than resist, for instance, the archaic book-ordering system in the Bodleian Library with technological mortification, I discovered the treasure in embracing its seeming quirkiness. Often, when the wrong book came up from the annals after my order, I found it to be right in some way after all. Oxford often works such. After one particularly serendipitous day of research, I asked Robert, the usual morning porter on duty at the Bodleian Library, about the lack of any kind of sophisticated security system, especially in one of the world’s most famous libraries. The Bodleian was not a loaning library, though you were allowed to work freely amid priceless artifacts. Individual college libraries entrusted you to simply sign a book out and then return it when you were done. “It’s funny; Americans ask me about that all the time,” Robert said as he stirred his tea. “But then again, they’re not used to having u in honour,” he said with a shrug.

DevOps and its resulting technical, architectural, and cultural practices represent a convergence of many philosophical and management movements (including): Lean, Theory of Constraints, Toyota production system, resilience engineering, learning organizations, safety culture, Human factors, high-trust management cultures, servant leadership, organizational change management, and Agile methods.

Japan, a country that had done its best to have no contact with strangers and to seal out the rest of the world. Its economy and politics were dominated by feudal agriculture and a Confucian hierarchical social structure, and they were steadily declining. Merchants were the lowest social class, and trading with foreigners was actually forbidden except for limited contact with China and the Dutch. But then Japan had an unexpected encounter with a stranger—Commodore Matthew Perry—who burst in on July 8, 1853, demanding that Japan’s ports be open to America for trade and insisting on better treatment for shipwrecked sailors. His demands were rebuffed, but Perry came back a year later with a bigger fleet and more firepower. He explained to the Japanese the virtues of trading with other countries, and eventually they signed the Treaty of Kanagawa on March 31, 1854, opening the Japanese market to foreign trade and ending two hundred years of near isolation. The encounter shocked the Japanese political elites, forcing them to realize just how far behind the United States and other Western nations Japan had fallen in military technology. This realization set in motion an internal revolution that toppled the Tokugawa Shogunate, which had ruled Tokyo in the name of the emperor since 1603, and brought Emperor Meiji, and a coalition of reformers, in his place. They chose adaptation by learning from those who had defeated them. They launched a political, economic, and social transformation of Japan, based on the notion that if they wanted to be as strong as the West they had to break from their current cultural norms and make a wholesale adoption of Western science, technology, engineering, education, art, literature, and even clothing and architecture. It turned out to be more difficult than they thought, but the net result was that by the late nineteenth century Japan had built itself into a major industrial power with the heft to not only reverse the unequal economic treaties imposed on it by Western powers but actually defeat one of those powers—Russia—in a war in 1905. The Meiji Restoration made Japan not only more resilient but also more powerful.

Generating a system architecture is not a deterministic process. It requires careful consideration of business requirements, technology choices, existing infrastructure and systems, and actual physical resources, such as budget and manpower.

When Mathematics unfold through Origamis, when video games target Medicine and Education, when architecture embraces nature, when we defy gravity, when physics dance, and dance clubs play Einstein, when we stop playing war, when TV starts saying something, when we produce without wasting, when engineering meets humanity’s primary needs, when all of these are not just casualties, but a standard we all live UP to: Then we’ll know. I’ll know: we really live in the 21st century

Frank Gehry’s office began to recognize the benefits of CAD/CAM and reciprocated in a technology transfer back to architecture, fusing computers with engineering, fabrication, art and architecture.

the architecture that our services operate within dictates how we test and deploy our code. This

It’s actually the same,” said Frank, stating the obvious, as if Muriel wasn’t aware, “as your digitized cafeteria. These types of places are a cousin to that technological development. Economies of unthinkably vast scale allow the production of cheap, unsubtle food that overrides your limbic system with heavy, carnal signals so as to hide its exact resemblance to slow-acting poison. And this so-called food is served to you by a member of an underclass practically invisible to you, untouchable by you, unspeakable to except perhaps to complain and unspeakable of except perhaps to yourself with subconscious and subvocalized disdain, and yet, almost needless to say, a person whose destiny could have been exchanged for your own but for capricious circumstance. And this meal, so-called, once placed on a tray for you to take to your seat, will be eaten within an almost indestructible yet disposable shelter composed of polyurethanes, petrochemicals, fiberglass, and the occasional piece of metal—restaurant castles, in other words, that rival geodesic domes in their modular, architectural ingeniousness.

We will actively manage this technical debt by ensuring that we invest at least 20% of all Development and Operations cycles on refactoring, investing in automation work and architecture and non-functional requirements (NFRs, sometimes referred to as the “ilities”), such as maintainability, manageability, scalability, reliability, testability, deployability, and security. Figure 11: Invest 20% of cycles on those that create positive, user-invisible value (Source: “Machine Learning and Technical Debt with D. Sculley,” Software Engineering Daily podcast, November 17, 2015,

In the technology value stream, we optimize for downstream work centers by designing for operations, where operational non-functional requirements (e.g., architecture, performance, stability, testability, configurability, and security) are prioritized as highly as user features.

All joking aside, these diagrams do suffer from one or more of the following problems: • Notation (e.g. colour coding, shapes, etc) is not explained or is inconsistent. • The purpose and meaning of elements is ambiguous. • Relationships between elements are missing or ambiguous. • Generic terms such as “business logic” are used. • Technology choices (or options, if doing up front design) are omitted. • Levels of abstraction are mixed. • Too much or too little detail. • No context or a logical starting point.

This kind of service-oriented architecture allows small teams to work on smaller and simpler units of development that each team can deploy independently, quickly, and safely. Shoup notes, “Organizations with these types of architectures, such as Google and Amazon, show how it can impact organizational structures, [creating] flexibility and scalability. These are both organizations with tens of thousands of developers, where small teams can still be incredibly productive.

how we organize our teams has a powerful effect on the software we produce, as well as our resulting architectural and production outcomes. In

Amazon realized the importance of recruiting developers early  —  moving its entire organization to services-based interfaces. At the time, this was revolutionary; while everyone was talking about “Service Oriented Architectures,” almost no one had built one. And certainly no one had built one at Amazon’s scale. While this had benefits for Amazon internally, its practical import was that, if Amazon permitted it, anyone from outside Amazon could interact with its infrastructure as if they were part of the company. Need to provision a server, spin up a database, or accept payments? Outside developers could now do this on Amazon’s infrastructure as easily as employees. Suddenly, external developers could not only extend Amazon’s own business using their services  —  they could build their own businesses on hardware they rented from the one-time bookstore, now a newly minted technology vendor.

When we have a tightly-coupled architecture, small changes can result in large scale failures. As

Every decision we make for our projects, be it technology, process or people related, can be a viewed as a form of investment. Investments come associated with a cost, which may or may not be monetary, and carry trust that they will eventually pay off. Our employers choose to offer us salaries in the hope that this investment will positively affect the outcome of their venture. We decide to follow a specific development methodology in the hope that it will make the team more productive. We choose to spend a month redesigning the physical architecture of an application in the belief that it will be beneficial in the long run.

I thought I’d “missed the wave” of some technology or another. What I didn’t appreciate at the time is that new technologies are a lot like buses—one comes every 15 minutes or so. As architects, we have to remember that we cannot stop change, but we can manage it.

Standing before costly objects of technological beauty, we may be tempted to reject the possibility of awe, for fear that we could grow stupid through admiration. We may feel at risk of becoming overimpressed by architecture and engineering, of being dumbstruck by the Bombardier trains that progress driverlessly between satellites or by the General Electric GE90 engines that hang lightly off the composite wings of a Boeing 777 bound for Seoul. And yet to refuse to be awed at all might in the end be merely another kind of foolishness.

These comments recall Turkle's distinction between two kinds of "transparency" in technological cultures. Modernist transparency is the notion that users can and should have access to the inner workings of a technology. It evokes the aesthetic of early relationships with cars in which one could "open the hood and see inside." Turkle contrasts this with an opposing, post-modern meaning of the term - the notion that something is transparent if you can use it without knowing how it works. Post-modern transparency allows the user to navigate the surface of a system without ever having to access its underlying mechanics. Are young engineers more susceptible to post-modern ways of seeing simulation?

Key goals include helping increase employee productivity while supporting new business requirements and technology trends, including IT consumerization, cloud computing, and access by a broader range of users. At the same time, the architecture is designed to reduce our attack surface and improve survivability—even as the threat landscape grows in complexity and maliciousness.