Infrastructure As Code Quotes

. . . it is a mistake to think that Marxism is simply a type of interpretation that takes the economic "sequence" as that ultimately privileged code into which the other sequences are to be translated. Rather, for Marxism the emergence of the economic, the coming into view of the infrastructure itself, is simply the sign of the approach of the concrete.

In this business, I find more value in working with hackers who abstract new realities from cast aside code and concepts than academics who regurgitate other people’s work and try to pawn it off as their own.

The near future will see robot suits that allow paraplegics to walk, designer drugs that melt away certain forms of cancer, and computer code being used as both an international currency and a weapon to destroy physical infrastructure halfway around the world.

Caste is the infrastructure of our divisions. It is the architecture of human hierarchy, the subconscious code of instructions for maintaining, in our case, a four-hundred-year-old social order. Looking at caste is like holding the country’s X-ray up to the light.

The collaboration between secretaries of state, election officials and the voting system manufacturers on the matter of enforcing this black box proprietary code secrecy with election systems, is nothing less than the commoditization and monetization of American Democracy

Women’s work is a natural resource that we don’t think we need to account for. Because we assume it will always be there. It’s considered invisible, indelible infrastructure.”10And because changing diapers, grocery shopping, doing laundry, cleaning the kitchen, and cooking dinner are all coded as “a natural resource,” this labor doesn’t require maintenance, upkeep, replenishing, or even materials as far as traditional economics is concerned.

These are private social infrastructures, there for the pleasure and convenience of first-tier staff members whose color-coded badges grant them access, but, crucially, not for the low-level temps and contractors who cook and clean in the same organization, and not for neighboring residents or visitors. These expensive, carefully designed social infrastructures work so well for high-level tech employees that they have little reason to patronize small local businesses—coffee shops, gyms, restaurants, and the like—that might otherwise benefit far more from the presence of a large employer.

This wasn’t the only mistake they made. They also botched the cleanup operation on the servers they could access. They had created a script called LogWiper.sh to erase activity logs on the servers to prevent anyone from seeing the actions they had taken on the systems. Once the script finished its job, it was also supposed to erase itself, like an Ouroboros serpent consuming its own tail. But the attackers bungled the delete command inside the script by identifying the script file by the wrong name. Instead of commanding the script to delete LogWiper.sh, they commanded it to delete logging.sh. As a result, the LogWiper script couldn’t find itself and got left behind on servers for Kaspersky to find. Also left behind by the attackers were the names or nicknames of the programmers who had written the scripts and developed the encryption algorithms and other infrastructure used by Flame. The names appeared in the source code for some of the tools they developed. It was the kind of mistake inexperienced hackers would make, so the researchers were surprised to see it in a nation-state operation. One, named Hikaru, appeared to be the team leader who created a lot of the server code,

The weakness of ‘learning to code’ alone might be argued in the opposite direction too: you should be able to understand technological systems without having to learn to code at all, just as one should not need to be a plumber to take a shit, nor to live without fear that your plumbing system might be trying to kill you. The possibility that your plumbing system is indeed trying to kill you should not be discounted either: complex computational systems provide much of the infrastructure of contemporary society, and if they are not safe for people to use, no amount of education in just how bad they are will save us in the long run.

What is scarce? Surely time is scarce? This is true in the sense that we get only one life, but yet again there are ways in which competition and how we use our time can make us feel an artificial sense of time scarcity. Each time we are able to build on the work of others with confidence, each time we use the elements of life pulled from our commonwealth of agricultural knowledge, we bundle time, and so get the benefit of having multiple lifetimes. Each time nature uses genetic code that has been developed over millions of years, millions of years of development are collapsed into something that works in our lifetimes. Each time we add to that collection, we are putting our lifetimes' work into a useful form for the benefit of future generations. At the same time, yes, we each have only our own single lives in which to pursue happiness. The goal is to spend as much of that time in a framework of sharing abundance rather than having it squeezed into a life of scarcity and competition. In contrast, we need not look far to find lots of frustrating examples in which our time is treated as abundant when we would rather have it be valued as scarce. It happens each time we must stand in line at the DMV, fill out redundant forms at the hospital, reproduce others' efforts by spending time searching for knowledge or data that already exists somewhere, create a report that no one reads. In those cases, we are creating and living in artificial and unnecessary time scarcity. Time is indeed one of the most curious elements of life, especially since our lifetimes and those of plants and animals all move at different rates. We know, for example, that the urgency to address climate change is really on our human scale, not geologic scale. The Earth has been through greater upheavals and mass extinctions and will likely go through them again, but for the narrowest of narrow bands of human history on Earth, we require very specific conditions for us to continue to thrive as a species. To keep our planet within a habitable and abundant balance, we have, as Howard Buffet noted, only 'forty seasons' to learn and adjust. That is why building on one another's work is so important. One farmer can have the benefit of forty seasons and pass some of that experience down, but if 1,000 farmers do the same, there is the collective benefit of 1,000 years in a single year. If a million people participate, then a million years of collective experience are available. If we are then able to compound knowledge across generations and deepen our understanding of human and natural history, we add even greater richness. It is in this way of bundling our experiences for continual improvement, with compound interest, that time shifts from a scarce resource to being far less of a constraint, if not truly abundant. However, for time to be compounded, knowledge must be shared, and real resources, energy, and infrastructure must exist and function to support and grow our commonwealth of knowledge.

Infrastructure as Code.” If you’re going to do operations reliably, you need to make it reproducible and programmatic.

Stuxnet is perhaps the most infamous of APTs, but it has cousins such as Flame and Duqu, along with many others yet to be discovered. Worse, now that Stuxnet, a tool developed to attack industrial control systems and take power grids off-line, is out in the wild and available for download, it has been extensively studied by Crime, Inc., which is rapidly emulating its techniques and computer code to build vastly more sophisticated attacks. The deep challenge society faces from the growth of the malware-industrial complex is that once these offensive tools are used, they have a tendency to leak into the open. The result has been the proliferation of open-source cyber weapons now widely available on the digital underground for anybody to redesign and arm as he or she sees fit. How long will it be before somebody picks up one of these digital Molotov cocktails and lobs it back at us with the intent of attacking our own critical infrastructure systems? Sadly, preparations may already be under way.

As we learned in response to the last great economic calamity to confront the country, to ensure broad prosperity government has four crucial roles to play: first, to help people weather the vicissitudes that easily plunge families into poverty, for instance job loss or ill health; second, to provide escalators of upward mobility, such as quality schooling, higher education, and mortgage assistance; third, to build the nation’s infrastructure, thus laying the groundwork for the next great economic boom; and fourth, to rein in marketplace abuses through regulation, and to prevent excessive concentrations of wealth through progressive taxation. This is the New Deal liberal vision that propelled the largest expansion of the middle class ever seen, and that once enjoyed broad support across the whole country. Throughout

physical sharing and exchange of computer tapes and disks on which the code was recorded. In current Internet days, rapid technological advances in computer hardware and software and networking technologies have made it much easier to create and sustain a communal development style on ever-larger scales. Also, implementing new projects is becoming progressively easier as effective project design becomes better understood, and as prepackaged infrastructural support for such projects becomes available on the Web. Today, an open source software development project is typically initiated by an individual or a small group seeking a solution to an individual's or a firm's need. Raymond (1999, p. 32) suggests that "every good work of software starts by scratching a developer's personal itch" and that "too often software developers spend their days grinding away for pay at programs they neither need nor love. But not in the (open source) world...." A project's initiators also generally become the project's "owners" or "maintainers" who take on responsibility for project management." Early on, this individual or group generally develops a first, rough version of the code that outlines the functionality envisioned. The source code for this initial version is then made freely available to all via downloading from an Internet website established by the project. The project founders also set up infrastructure for the project that those interested in using or further developing the code can use to seek help, provide information or provide new open source code for others to discuss and test. In the case of projects that are successful in attracting interest, others do download and use and "play with" the code-and some of these do go on to create new and modified code. Most then post what they have done on the project website for use and critique by any who are interested. New and modified code that is deemed to be of sufficient quality and of general interest by the project maintainers is then added to the authorized version of the code. In many projects the privilege of adding to the authorized code is restricted to only a few trusted developers. These few then serve as gatekeepers for code written by contributors who do not have such access (von Krogh and Spaeth 2002). Critical tools and infrastructure available to open source software project participants includes email lists for specialized purposes that are open to all. Thus, there is a list where code users can report software failures ("bugs") that they encounter during field use of the software. There is also a list where those developing the code can share ideas about what would be good next steps for the project, good features to add, etc. All of these lists are open to all and are also publicly archived,

There had to be something near racial parity in the early stages because setting up the infernal machine required at least as many Europeans as Africans. Consequently, the original contact language had to be not too far from the language of the slave owners. Because at this stage Europeans were teaching Africans what they had to do, the contact language had to be intelligible to native speakers of the European language. Because so many interactions were between Europeans and Africans, the latter would have much better access to that European language than at any later stage in plantation history. We should remember that Africans, unlike modern Americans, do not regard monolingualism as a natural state, but expect to have to use several languages in the course of their lives. (In Ghana, our house-boy, Attinga, spoke six languages-two European, four African-and this was nothing out of the ordinary.) But as soon as the infrastructure was in place, the slave population of sugar colonies had to be increased both massively and very rapidly. If not, the plantation owners, who had invested significant amounts of capital, would have gone bankrupt and the economies of those colonies would have collapsed. When the slave population ballooned in this way, new hands heavily outnumbered old hands. No longer did Europeans instruct Africans; now it was the older hands among the Africans instructing the new ones, and the vast majority of interactions were no longer European to African, the were African to African. Since this was the case, there was no longer any need for the contact language to remain mutually intelligible with the European language. Africans in positions of authority could become bilingual, using one language with Europeans, another with fellow Africans. The code-switching I found in Guyana, which I had assumed was a relatively recent development, had been there, like most other things, from the very beginning. In any case, Africans in authority could not have gone on using the original contact language even if they'd wanted to. As we saw, it would have been as opaque to the new arrivals as undiluted French or English. The old hands had to use a primitive pidgin to communicate with the new hands. And, needless to add, the new hands had to use a primitive pidgin to communicate with one another. Since new hands now constituted a large majority of the total population, the primitive pidgin soon became the lingua franca of that population. A minority of relatively privileged slaves (house slaves and artisans) may have kept the original contact language alive among themselves, thus giving rise to the intermediate varieties in the continuum that confronted me when I first arrived in Guyana. (For reasons still unknown, this process seems to have happened more often in English than in French colonies.) But it was the primitive, unstructured pidgin that formed the input to the children of the expansion phase. Therefore it was the children of the expansion phase-not the relatively few children of the establishment phase, the first locally born generation, as I had originally thought-who were the creators of the Creole. They were the ones who encountered the pidgin in its most basic and rudimentary form, and consequently they were the ones who had to draw most heavily on the inborn knowledge of language that formed as much a part of their biological heritage as wisdom teeth or prehensile hands.

Programming languages, their features, readability, and interoperation Code reuse across platforms (server vs web vs mobile) Early error detection (compile-time vs runtime error detection, breadth of validation) Availability and cost of hiring the right talent; learning curve for new hires Readability and refactorability of code Approach to code composition, embracing the change Datastore and general approach to data modeling Application-specific data model, and the blast radius from changing it Performance and latency in all tiers and platforms Scalability and redundancy Spiky traffic patterns, autoscaling, capacity planning Error recovery Logging, telemetry, and other instrumentation Reducing complexity User interfaces and their maintainability External APIs User identity and security Hardware and human costs of the infrastructure and its maintenance Enabling multiple concurrent development workstreams Enabling testability Fast-tracking development by adopting third-party frameworks

items. While Monster Hunter included a single-player mode, its appeal was its online play. The five-man crew who had worked with Capcom thought some the game's networking code looked awfully familiar. "Same network infrastructure, same style of gameplay [as the PS2 Diablo title]," Joe Morrissey said. [Return to Chapter]

Infrastructures.org

and Medicaid, which would help expand coverage and bring down costs. The other thing we should be honest about is how hard it’s going to be, no matter what we do, to create significant economic opportunity in every remote area of our vast nation. In some places, the old jobs aren’t coming back, and the infrastructure and workforce needed to support big new industries aren’t there. As hard as it is, people may have to leave their hometowns and look for work elsewhere in America. We know this can have a transformative effect. In the 1990s, the Clinton administration experimented with a program called Moving to Opportunity for Fair Housing, which gave poor families in public housing vouchers to move to safer, middle-income neighborhoods where their children were surrounded every day by evidence that life can be better. Twenty years later, the children of those families have grown up to earn higher incomes and attend college at higher rates than their peers who stayed behind. And the younger the kids were when they moved, the bigger boost they received. Previous generations of Americans actually moved around the country much more than we do today. Millions of black families migrated from the rural South to the urban North. Large numbers of poor whites left Appalachia to take jobs in Midwestern factories. My own father hopped a freight train from Scranton, Pennsylvania, to Chicago in 1935, looking for work. Yet today, despite all our advances, fewer Americans are moving than ever before. One of the laid-off steelworkers I met in Kentucky told me he found a good job in Columbus, Ohio, but he was doing the 120-mile commute every week because he didn’t want to move. “People from Kentucky, they want to be in Kentucky,” another said to me. “That’s something that’s just in our DNA.” I understand that feeling. People’s identities and their support systems—extended family, friends, church congregations, and so on—are rooted in where they come from. This is painful, gut-wrenching stuff. And no politician wants to be the one to say it. I believe that after we do everything we can to help create new jobs in distressed small towns and rural areas, we also have to give people the skills and tools they need to seek opportunities beyond their hometowns—and provide a strong safety net both for those who leave and those who stay. Whether it’s updating policies to meet the changing conditions of America’s workers, or encouraging greater mobility, the bottom line is the same: we can’t spend all our time staving off decline. We need to create new opportunities, not just slow down the loss of old ones. Rather than keep trying to re-create the economy of the past, we should focus on making the jobs people actually have better and figure out how to create the good jobs of the future in fields such as clean energy, health care, construction, computer coding, and advanced manufacturing. Republicans will always be better at defending yesterday. Democrats have to be in the future business. The good news is we have

The latter pattern is what has become known as immutable infrastructure, where manual changes to the production environment are no longer allowed—the only way production changes can be made is to put the changes into version control and re-create the code and environments from scratch. By doing this, no variance is able to creep into production.

Senator Markey’s Cyber Shield Act can work! Start the conversations with the basics: Use a QR code that attaches to a dynamic database that runs an artificial intelligence algorithm to calculate the score. Let’s not make this more difficult than it is.

colour coding to decipher. Can you work out what the colour coding means? Is it related to input vs output functions? Or perhaps it’s business vs infrastructure? Existing vs new? Buy vs build? Or maybe different people simply had different colour pens! Who knows.

Miguel Antunes, R&D Principle Software Engineer at OutSystems, a low-code platform vendor, relayed an example of this very challenge. Their Engineering Productivity team at OutSystems was five years old. The team’s mission was to help product teams run their builds efficiently, maintain infrastructure, and improve test execution. The team kept growing and took on extra responsibilities around continuous integration (CI), continuous delivery (CD), and infrastructure automation.

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)

Jason Hudak to head the platform team. Jason had worked at Yahoo for more than a decade, building the infrastructure to support their thousands of engineers. Jason is probably not what you imagine when you think of a software engineer. He’s a ruddy-faced Texan and a former Marine. He went to Texas Tech and studied business, not computer science. He’s more or less self-taught, having learned to write code after landing a job at a tech company in the 1990s and studying alongside engineers who recognized his potential. Jason spends his free time snorkeling, cycling, and hunting wild boars in Texas.

Like other old houses, America has an unseen skeleton, a caste system that is as central to its operation as are the studs and joists that we cannot see in the physical buildings we call home. Caste is the infrastructure of our divisions. It is the architecture of human hierarchy, the subconscious code of instructions for maintaining, in our case, a four-hundred-year-old social order. Looking at caste is like holding the country’s X-ray up to the light

Rejuvenation: These advances slow the aging process by helping bodily systems “act” younger. You can go through a process that has an effect on the infrastructure, just like a massage may loosen up sore muscles or an oil change peps up an engine.

I believe in God,” says my nan, in a way that makes the idea of an omnipotent, unifying frequency of energy manifesting matter from pure consciousness sound like a chore. An unnecessary chore at that, like cleaning under the fridge. I tell her, plucky little seven-year-old that I was, that I don’t. This pisses her off. Her faith in God is not robust enough to withstand the casual blasphemy of an agnostic tot. “Who do you think made the world, then?” I remember her demanding as fiercely as Jeremy Paxman would later insist I provide an instant global infrastructure for a post-revolutionary utopia. “Builders,” I said, thinking on my feet. This flummoxed her and put her in a bad mood for the rest of the walk. If she’d hit back with “What about construction at a planetary or galactic level?” she’d’ve had me on the ropes. At that age I wouldn’t’ve been able to riposte with “an advanced species of extraterrestrials who we have been mistakenly ascribing divine attributes to due to our own technological limitations” or “a spontaneous cosmic combustion that contained at its genesis the code for all subsequent astronomical, chemical, and biological evolution.” I probably would’ve just cried. Anyway, I’m supposed to be explaining the power of forgiveness, not gloating about a conflict in the early eighties in which I fared well against an old lady. Since getting clean from drugs and alcohol I have been taught that I played a part in the manufacture of all the negative beliefs and experiences from my past and I certainly play a part in their maintenance. I now look at my nan in another way. As a human being just like me, trying to cope with her own flaws and challenges. Fearful of what would become of her sick daughter, confused by the grandchild born of a match that she was averse to. Alone and approaching the end of her life, with regret and lacking a functioning system of guidance and comfort. Trying her best. Taking on the responsibility of an unusual little boy with glib, atheistic tendencies, she still behaved dutifully. Perhaps this very conversation sparked in me the spirit of metaphysical inquiry that has led to the faith in God I now have.

Regardless, in this world, this world where everything was linked, where data ruled all, where cryptographic codes had replaced physical locks on the world’s wealth, on its infrastructure, on its weapons… In this world a being able to process information more rapidly than humans was the ultimate threat.

DBAs work exactly in the middle of sofware and hardware, between developers and operators and between applications and infrastructure. This position provides DBAs with all sorts of challenges, from a badly written SQL statement from developers to storage bottlenecks, from network latency problem to metadata definition, and from coding database procedures to defining hardware requirements for a new database.

I was an ephemeral infrastructure to their code.

The infrastructure that supports our continuous integration and continuous deployment processes also presents a new surface area vulnerable to attack. For instance, if someone compromises the servers running the deployment pipeline that has the credentials for our version control system, it could enable someone to steal source code. Worse, if the deployment pipeline has write access, an attacker could also inject malicious changes into our version control repository and, therefore, inject malicious changes into our application and services.

Myth—DevOps is Just “Infrastructure as Code” or Automation: 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. This goes far beyond just automation.

Build, test, iterate. That’s what I’d needed at all three of my prior companies. Then I thought about what we’d been building at AWS—infrastructure as Application Programming Interfaces (APIs) that developers could invoke with a few lines of code, and for pennies per use. Modernizing communications for the software era seemed like a big problem, and I thought there was a way to solve it: by turning communication into APIs for software developers.

At AWS, however, a lot of customers were just ordinary developers. Individual engineers or department managers could spin up a server and storage capacity at AWS just by entering a credit card number. When the company started using that application the IT department didn’t move the code back to their in-house data center. They left it on AWS. As their usage went up, so did their monthly bills. And because of it, developers gained much more influence over how companies bought infrastructure.

Like me, Ryan doesn’t believe that founders should start with code. “Do shitty work people love at first,” he says. As more and more infrastructure gets built by new businesses (including, perhaps, the one you’re working on now), it is getting cheaper, faster, and more accessible to build an MVP without code. What that means is that you shouldn’t wait until tomorrow to get started. The lower the barriers to entry, the more competition you will have.

Between the black box proprietary code, barebones computers we call voting machines and a mass of completely unqualified election officials, our election system is up for grabs to anybody with even a modest interest and some script kiddie capability. The cyber-kinetic attack surface here is wide open.

because our workforce is so productive; our infrastructure and Internet bandwidth are so advanced; our openness to talent from anywhere is second to none; our funding for basic research is so generous; our rule of law, patent protection, and investment- and manufacturing-friendly tax code is superior to what can be found in any other country; and our openness to collaboration is unparalleled—all because we have updated and expanded our formula for success.

We want America in the twenty-first century to be the launching pad where everyone in the world comes to launch his or her moon shot. We want it to be the place where innovators and entrepreneurs the world over come to locate all or part of their operations because our workforce is so productive; our infrastructure and Internet bandwidth are so advanced; our openness to talent from anywhere is second to none; our funding for basic research is so generous; our rule of law, patent protection, and investment- and manufacturing-friendly tax code is superior to what can be found in any other country; and our openness to collaboration is unparalleled—all because we have updated and expanded our formula for success.

The sociopaths’ goal is to wring every last dollar from the system, and any investment that could not be fully realized within Boomer lifetimes was to be avoided. Therefore, the nation’s infrastructure, built by the Boomers’ parents and once the world’s finest, was allowed to decay. Henceforth, state-sponsored research would be radically curtailed. Higher education was neglected; the Boomers had their cost-free diplomas in hand, so meaningful reform and costly subsidies were no longer relevant. Public tuition, formerly zero, could rise dramatically. Even better, the loans taken out to meet those new educational bills, including those produced by the Boomer-created plague of for-profit colleges, could be converted into today’s $1.3 trillion of student loans, profits on which the Boomers harvest and shall so forever, thanks to a modification of the bankruptcy code in 2005 that makes student debt nearly impossible to discharge. The Flower Child of Berkeley would become the Merchant of Midtown. Just

We are perfectly innocent, harmless hominids. Nothing to see here. We certainly aren’t hacking into your infrastructure

on as you learn more complex hacks and tests, you will need a target machines suited for such hacks. The best way to learn to hack Linux systems is to download and install the Metasploitable Linux distribution. The Metasploitable distro is purposefully made to incorporate vulnerabilities that learners like yourself can use for security testing and hacking purposes. The best part is that you can set it up to boot just like an operating system you use for your everyday computing needs or you can set it up in VirtualBox or VMware Workstation platforms. Using Metasploitable Linux OS for your hacking practice is the best way to understand more about the Linux infrastructure, security setup, and how to discover and exploit its vulnerabilities. You can read the documentation of Metasploitable and download the installation ISO from Rapid 7

One of the arguments often made in response to weak public understanding of technology is a call to increase technological education - in its simplest formulation, to learn to code. Such a call is made frequently by politicians, technologists, pundits and business leaders, and it is often advanced in nakedly functional and pro-market terms: the information economy needs more programmers, and young people need jobs in the future. This is a good start, but learning to code is not enough, just as learning to plumb a sink is not enough to understand the complex interactions between water tables, political geography, aging infrastructure, and social policy that define, shape and produce actual life support systems in society. A simply functional understanding of systems is insufficient; one needs to be able to think about histories and consequences too. Where did these systems come from, who designed them and what for, and which of these intentions still lurk within them today?

Computational thinking is an extension of what others have called solutionism: the belief that any given problem can be solved by the application of computation. Whatever the practical or social problem we face, there is an app for it. But solutionism is insufficient too; this is one of the things that our technology is trying to tell us. Beyond this error, computational thinking supposes - often at an unconscious level - that the world really is like the solutionists propose. It internalizes solutionism to the degree that it is impossible to think or articulate the world in terms that are not computable. Computational thinking is predominant in the world today, driving the worst trends in our society and interactions, and must be opposed by a real systemic literacy. If philosophy is that fraction of human thought dealing with that which cannot be explained by the sciences, then systemic literacy is the thinking that deals with a world that is not computable, while acknowledging that it is irrevocably shaped and informed by computation. The weakness of 'learning to code' alone might be argued in the opposite direction too: you should be able to understand technological systems without having to learn to code at all, just as one should not need to be a plumber to take a shit, nor to live without fear that your plumbing might be trying to kill you. The possibility that your plumbing system is indeed trying to kill you should not be discounted either: complex computational systems provide much of the infrastructure of contemporary society, and if they are not safe for people to use, no amount of education in just how bad they are will save us in the long run.

Today the cloud is the central metaphor of the internet: a global system of great power and energy that nevertheless retains the aura of something noumenal and numnious, something almost impossible to grasp. We connect to the cloud; we work in it; we store and retrieve stuff from it; we think through it. We pay for it and only notice it when it breaks. It is something we experience all the time without really understanding what it is or how it works. It is something we are training ourselves to rely upon with only the haziest of notions about what is being entrusted, and what it is being entrusted to. Downtime aside, the first criticism of this cloud is that it is a very bad metaphor. The cloud is not weightless; it is not amorphous, or even invisible, if you know where to look for it. The cloud is not some magical faraway place, made of water vapor and radio waves, where everything just works. It is a physical infrastructure consisting of phone lines, fibre optics, satellites, cables on the ocean floor, and vast warehouses filled with computers, which consume huge amounts of water and energy and reside within national and legal jurisdictions. The cloud is a new kind of industry, and a hungry one. The cloud doesn't just have a shadow; it has a footprint. Absorbed into the cloud are many of the previously weighty edifices of the civic sphere: the places where we shop, bank, socialize, borrow books, and vote. Thus obscured, they are rendered less visible and less amenable to critique, investigation, preservation and regulation. Another criticism is that this lack of understanding is deliberate. There are good reasons, from national security to corporate secrecy to many kinds of malfeasance, for obscuring what's inside the cloud. What evaporates is agency and ownership: most of your emails, photos, status updates, business documents, library and voting data, health records, credit ratings, likes, memories, experiences, personal preferences, and unspoken desires are in the cloud, on somebody else's infrastructure. There's a reason Google and Facebook like to build data centers in Ireland (low taxes) and Scandinavia (cheap energy and cooling). There's a reason global, supposedly post-colonial empires hold onto bits of disputed territory like Diego Garcia and Cyprus, and it's because the cloud touches down in these places, and their ambiguous status can be exploited. The cloud shapes itself to geographies of power and influence, and it serves to reinforce them. The cloud is a power relationship, and most people are not on top of it. These are valid criticisms, and one way of interrogating the cloud is to look where is shadow falls: to investigate the sites of data centers and undersea cables and see what they tell us about the real disposition of power at work today. We can seed the cloud, condense it, and force it to give up some of its stories. As it fades away, certain secrets may be revealed. By understanding the way the figure of the cloud is used to obscure the real operation of technology, we can start to understand the many ways in which technology itself hides its own agency - through opaque machines and inscrutable code, as well as physical distance and legal constructs. And in turn, we may learn something about the operation of power itself, which was doing this sort of thing long before it had clouds and black boxes in which to hide itself.

Like other old houses, America has an unseen skeleton, a caste system that is as central to its operation as are the studs and joists that we cannot see in the physical buildings we call home. Caste is the infrastructure of our divisions. It is the architecture of human hierarchy, the subconscious code of instructions for maintaining, in our case, a four-hundred-year-old social order.