6 Living on Shaking Ground
Chapter 6
Nature’s Indifference and the Illusion of Control
Engineering
“Man is not the lord of beings. Man is the shepherd of being.” — Martin Heidegger
I didn’t so much leave Los Angeles as drift out of it—like smoke that hadn’t made up its mind whether to rise or linger. The riot had cracked the city, graduation was inching forward, and my Corolla was already complaining that it wasn’t Dante-ready for the full tour of Inferno. Yet for reasons known only to the gods of poor timing, I stayed just long enough to be caught between chapters. I was headed to Silicon Valley in spirit, but still sleeping within helicopter range of SC.
When I finally crossed the county line for good, I told myself I was entering the land of certainty. LA had burned; surely the Valley would offer something calmer. I’d trade smoke for circuits, chaos for code, and beer cans for business parks. That was the theory.
The reality resembled a suburban distillery for ambition. Every garage buzzed with a half-funded dream; every café smelled of optimism, caffeine, and someone’s failed IPO. People spoke in acronyms the way monks whisper prayers—TCP/IP on their tongues, venture capital in their bloodstream. Even the air felt patent-pending.
I arrived with one faded student ID, thirty-six copies of my résumé, and enough leftover idealism to power a small LED. My “office” was a mom-and-pop consultancy tucked inside an affluent suburb—half workshop, half hermitage. The proprietor, who quickly became my mentor, was a man who could troubleshoot a hard drive by ear and a human being by anecdote. 50% sage, 50% savant, and 110% go-getter. He optimized systems, and motivated people; and lived by an iron code: Work hard, think deep, push harder, and never, ever leave a dollar on the table. He called it a simple life!
We talked about everything: ideology, economics, servo motors, lasers, human motives, procurement nightmares, marriages, and why organizations look stable only in their brochures. He was the first person I’d met who could go from Fourier transforms to philosophy without changing facial expression.
He liked me, inexplicably. And so he taught me.
A Seer’s Lesson on Systems
My days were spent hunched over a laser-guided servo-writer for hard drives—a machine so finicky that a sneeze could knock a calibration off by microns. My nights were spent absorbing his lesson of the week, often delivered with the casual authority of a man who has outlived several industries.
When I once suggested solid-state storage—no moving parts, no crashes—he shook his head.
First came the engineering explanation: supplier networks, economies of scale, customer psychology, tactile familiarity, and how reliability itself requires a dose of expected failure.
Then came the punchline: “Son, people don’t trust things that never fail. They just sit there waiting for the crash.”
He wasn’t wrong. Every technology—like every human—carries an acceptable quota of disaster. The trick is to make failure look intentional.
In the Valley, they called it iteration. He called it life.
Engineering an Endeavor
A strange coincidence still frames this moment. As I was preparing to graduate and drift north, NASA launched Space Shuttle Endeavour—the ship built to replace Challenger. Endeavour was humanity’s apology note, our systematized attempt to restore what the explosion had broken six years earlier.
At the time of writing, it now sits at the California Science Center across from USC—staring directly at the city that once burned around me, as if waiting for my book to catch up.
The symbolism was almost comically on-the-nose:
Chapter 3 upheaval: Challenger—the limit of the brain’s tool-making.
Chapter 6 upheaval: Northridge—the limit of human shelter against nature.
Correction: Endeavour—the human attempt to rebuild the sky and pretend we can control the tremors below.
Watching that launch back then felt like watching systems wake up. Procurement, materials, design reviews, simulation, software, valves, tiles, bolts. Every piece remembered its purpose, and for 8½ minutes the entire species pretended entropy was optional.
It was beautiful. It was terrifying. It was human.
Where All Systems Begin
Endeavour was just the latest in a lineage of shelters we’ve built against the indifference of physics—from huts lashed with rope to steel cages bolted against the sky. The technology changes; the psychology doesn’t. Every structure is a wager that ingenuity can out-engineer entropy. Every roof is a declaration of faith in ground that often refuses the courtesy.
And that’s where this chapter begins: with the oldest human delusion and the youngest human triumph – that we can build systems strong enough to keep the shaking of the worlds at bay.
Before there were cities, codes, or cathedrals, we had a few sticks, a ring of fire, and the hope that the wind would stay polite.
The Architecture of Survival
From Huts to High-Rises — and the Lies We Tell the Earth
Before humanity learned to split atoms, launch shuttles, or argue on cable news, we learned something far more heroic: how to not die in the rain. Every civilization begins the same way—some cold, anxious primate dragging sticks into a circle and declaring it a house. That first hut wasn’t shelter so much as optimism with splinters.
And yet, it set the pattern for everything that followed: the belief that structure can outthink chaos. A roof is not just a roof. It is a thesis statement. It says: I reject meteors, marauders, and meteorology. The first walls were acts of defiance; the first beams, tiny philosophies. Humans did not evolve for safety—we invented it.
Shelter as Our First System
Shelter is where engineering quietly begins. Not as equations on a chalkboard, but as a late-afternoon decision about which way the wind usually blows and whether that tree is going to fall on you. Early builders had no blueprints, but they had hunches: build close enough for warmth, far enough for dignity; keep the fire inside and the wolves outside, not the other way around. The “code” was oral, experimental, and merciless: if your design failed, you didn’t get a second peer review.
From there, the hut learned to think in series. Branches lashed with vine became posts and beams. Posts and beams became walls and rafters. Walls and rafters became something like a plan. At Lepenski Vir, Çatalhöyük, Jericho, and all their unnamed cousins, you can already see the mental upgrade: people aligning their shelters with rivers, hills, stars, and each other. The ground plan became a guess about how the world works—a quiet equation in mud and timber.
Every wall is a sentence we write onto the landscape: This river will stay here. This hillside will not slide. This ground will not shake today.
The earth, for its part, has never signed these contracts. That is the first lie we tell it—that if we are careful enough with angles and joints, it will agree to behave.
Still, the lie is productive. Once a hut stands long enough, it stops being an experiment and becomes a habit. Habits turn into inheritance. Children grow up assuming “indoors” is a natural state, as if caves came with hinges and thatched roofs were born attached to families. We slowly domesticate not just plants and animals, but weather. We turn chaos into something that can be swept.
What began as a few branches tied with vines, then, quietly became the world’s earliest system:
Design: one brain squinting at the sky, deciding whether to trust the clouds.
Construction: multiple hands trying not to drop the same rock.
Testing: one unlucky cousin discovering the definition of “load-bearing.”
Crude or not, it worked often enough to repeat. And once it worked, we did what humans always do with working things: we scaled it. Clay huts became timber homes. Timber became stone. Stone became steel. Somewhere along the way, we began to believe we had finally tamed the planet.
Every city skyline is a boast. Every building permit is a prayer.
The Cooperation Machine
But shelter was never just a physical artifact. It was our first demonstration that humans could synchronize.
Building anything larger than a shed requires shared goals, shared labor, shared complaints, and at least one person insisting the blueprints are wrong
This was civilization’s original choreography: people aligning around a structure, merging their roles, and creating something none of them could build alone. Before corporations, before nations, before endless committee meetings— there was the construction crew.
Anthropologists call them “bands” and “tribes.” I call them the earliest DevOps teams.
Machines Made of Many Hands
Systems, Labor, and the Choreography of Collaboration
If huts are where engineering begins, barn raisings are where it starts needing a guest list.
At some point, a single family with a pile of sticks wasn’t enough. Roofs got heavier. Fields got bigger. Rivers needed taming. Walls needed lifting that no one pair of shoulders could manage. The answer was simple and suspiciously clever: add more shoulders.
A barn raising is engineering’s first team sport. No one shows up because of a project charter. They come because everyone knows that if your barn doesn’t stand this spring, theirs might not stand next year. Cooperation is not yet a management theory; it’s weather insurance.
From there, collaboration scales.
Irrigation canals in Mesopotamia, rice terraces in Asia, stone circles aligned with solstices, villages wrapped around wells—these weren’t just architectural choices, they were multi-person algorithms. Someone decides where to dig, someone decides who digs, someone keeps track of whose turn it is to get water and whose turn it is to pretend they don’t see the leak.
By the time we reach pyramids, aqueducts, and cathedrals, the pattern is unmistakable. The projects are too large, too heavy, and too far from the local stone pile to be anybody’s lone genius moment. They are machines made of many hands:
Designers and surveyors imagining shapes that do not yet exist.
Craftsmen and laborers translating that imagination into stone and wood.
Cooks and quartermasters keeping everyone vertical.
Overseers, priests, and bureaucrats insisting the whole apparatus is really for God, the emperor, or “the people,” depending on the decade.
The structure you end up with is not just a building; it’s a fossilized cooperation protocol. Somewhere inside a cathedral is the story of who planned, who hauled, who ate, who was allowed inside when it was finished, and who only ever saw the outside walls while going home sore.
This is where “engineering” starts to look a lot like social choreography. A wall that could be stacked in a day by ten people now takes months because there are schedules, inspections, resource constraints, and the arch must line up with the stained glass that has not yet arrived from three counties over. The price of ambition is coordination.
Fast-forward a few centuries and the choreography gets tighter.
Shipyards. Railroads. Telegraph lines. Factories. The Industrial Revolution did for labor what standardized parts did for machines: it made tasks modular. One person weaves, another spins, another minds the boiler, another writes everything down in a ledger. The old shared project becomes a series of narrow roles bolted together by timeclock and foreman.
From a distance, it’s magnificent. From the shop floor, it can feel like being a replaceable gear in someone else’s elegant diagram.
Engineers love to talk about systems. A bridge is a system. A power grid is a system. A space shuttle is a very expensive system that occasionally reminds you which part you forgot to model. What we talk about less is that every such system rides on another, less glamorous one: the system of work behind it.
To build a shuttle, you need not just materials and equations, but:
Layers of teams who understand only one slice of the whole.
Organizations that coordinate schedules across continents.
Paperwork dense enough to turn a human life into a stack of signatures and initials.
At some point, you can’t tell whether the shuttle is the goal and the bureaucracy the means, or the other way around.
Even modern “knowledge work” follows the same script, just with better coffee and worse posture. Software projects, hospitals, research labs, skyscraper sites—all of them are cooperation machines. People enter them with partial knowledge and partial agency, contribute their piece, and leave without ever holding the whole thing in their head.
This is both our strength and our vulnerability.
On the one hand, it lets us do things no individual brain could manage. No one person understands every bolt, equation, contract, and spreadsheet that keeps a city’s subway running. But the train still arrives (most days) because the system distributes understanding like a jigsaw puzzle.
On the other hand, fragmentation makes it easy for responsibility to evaporate. When something breaks—a bridge collapses, a factory explodes, a shuttle disintegrates on live television—everyone was involved, and somehow no one was. Each worker can honestly say, “My part passed inspection.” The failure lives in the gaps between parts, in the coordination layer that is everyone’s job and no one’s title.
From the outside, a dam or a data center looks like an object. From the inside, it feels like a fragile truce among deadlines, budgets, egos, safety codes, and whatever the river or server farm decides to do this week.
This chapter’s earthquake—Northridge—made that painfully literal. It wasn’t just buildings that shook; it was the social choreography behind them. Suddenly you could see which corners had been cut, which retrofits had been deferred, which “temporary” fixes had fossilized into permanent risk. Nature doesn’t read the org chart. It just loads the structure and lets the weakest link introduce itself.
We like to say “the system failed,” as if the system were something separate from the people who built and ran it. But if we zoom out a little, every engineered artifact is a stacked system:
Physics at the bottom.
Materials on top of that.
Design on top of that.
Labor and organization wrapped around it.
Culture, incentives, and myth draped over everything like a tarp.
When the bridge holds, we applaud engineering. When it falls, we blame gravity, or the last person who signed the form. What we rarely do is trace the whole choreography: who had the power to slow down, to double-check, to say no.
Industry, in that sense, is where engineering and sociology shake hands and then pretend they’ve never met. We draw neat diagrams of processes and workflows, then fill them with actual humans whose fears, hopes, and shortcuts do not fit in the boxes.
Later chapters will look at how we priced this choreography (economics) and how we tried to regulate it (politics). For now, it’s enough to notice that every large system is made of many hands, and that its fragility is not just in the steel and concrete, but in the way those hands are arranged.
Blueprints of Cooperation
Thus, the first architects were not just drawing buildings. They were drawing agreements.
You place that beam.
I lift this one.
Nobody sneezes while we’re doing it.
Those early blueprints were less about geometry and more about trust. Each line was a promise: I will do my part if you do yours.
This was the seed of every future system. Democracy. Corporations. The entire software industry. All of them rest on the fragile miracle of humans choosing—against every evolutionary impulse—to coordinate.
The Mechanics of Meaning
By the time I arrived in Silicon Valley, cooperation had been industrialized. Systems were not small, local, or personal anymore. They were sprawling symphonies of suppliers, subcontractors, procurement chains, engineers who insisted they weren’t the bottleneck, and managers who insisted they were
My mentor in the Valley—sage, savant, and occasional prophet of entropy—liked to remind me that every system has three parts:
The design: what the optimists believe
The implementation: what the realists manage
The maintenance: what the pessimists inherit
He was fluent in all three dialects, which is probably why disk-drive executives trusted him with their machinery and their metaphors.
We’d spend mornings discussing laser counters, servo alignment, and the correct number of curse words required to calibrate a spindle motor. Afternoons were for construction: he’d explain why two-by-fours lie, how concrete has moods, and why any structure—wooden or human—needs a little flex so it doesn’t shatter at the first argument.
He treated engineering and life as interchangeable puzzles. A disk drive was a marriage with bearings. A foundation was a social contract poured in gray. A servo system was a lesson in feedback: if the correction comes too late, everything shakes itself apart.
The Servo Writer as Parable
The servo-writer project was supposed to be simple: use lasers and counters to etch microscopic alignment tracks onto hard disks so data could find itself later.
But nothing about it was simple.
One misalignment: the drive screamed.
One dust particle: the track jittered.
One overlooked parameter: everything failed quietly until it didn’t.
It was a perfect teacher. Not just about electronics or mechanics, but about systems thinking:
No component existed alone.
Every subsystem affected every other.
Everything depended on the timing of everything else.
Silicon Valley likes to romanticize product launches, market disruption, and unicorn valuations. But the truth is simpler: The Valley runs on interdependence. On systems within systems. On hundreds of people solving thousands of tiny, unglamorous problems so one executive can announce “success” on a stage.
The Humor of Hierarchy
Somewhere between debugging servo noise and helping my mentor repair a roof beam he claimed was “just existentially fatigued,” I realized the secret of all systems:
The more complex they are,
the more they resemble the people who built them.
A system designed by optimists fails dramatically.
A system designed by pessimists never ships.
A system designed by realists ships, fails, is patched, fails differently, is patched again, and eventually becomes beloved.
This is the entire lifecycle of human cooperation, disguised as engineering.
The Corolla: A System with Opinions
My Corolla, meanwhile, developed the personality of a reluctant co-founder. It had carried me from the riots to the Valley, and it made its preferences clear:
It disapproved of potholes.
It refused to accelerate while thinking deeply.
And whenever I mentioned Seattle, it responded with a cough that translated roughly to: “This partnership needs boundaries.”
But like any good system, it kept me moving—even if it required the occasional pep talk, a prayer to the carburetor, and a ritual thump on the dashboard.
Why Systems Matter
What I learned in those short months—between servo alignments, construction detours, and half-philosophical drives through Palo Alto—was this:
Systems are how humans cheat fragility.
Together is the only technology that scales.
Our buildings may crack. Our disks may crash. Our blueprints may lie. Our cars may negotiate labor terms. But our ability to coordinate—to merge our imperfect efforts into something that stands upright long enough to matter—is the closest thing we have to magic. And, when the ground itself rebels, our systems of coordination are the only shelters we have.
Taming Time
Agriculture as Engineered Rhythm
If huts were our first argument with the weather, agriculture was our first argument with time. Once we had four walls that mostly stayed put, someone had the dangerous idea: What if the food stayed put too?
The so-called Neolithic Revolution was less a single moment than a collective “what if” stretched over millennia. Somewhere along a riverbank, a tired forager dropped a few seeds, came back months later, and realized the universe could be persuaded to repeat itself.
That was the first agricultural model:
Input: seeds, labor, optimism
Process: waiting, worrying, weeding
Output: calories (and new reasons to argue with neighbors)
If shelter was local engineering, agriculture was temporal engineering. You weren’t just building a roof over your head; you were building next autumn. To farm is to run a simulation in your head and bet your life on the result.
You have to:
Believe that seasons are patterns, not moods.
Believe that clouds can be read like spreadsheets.
Believe that the ground will remember what you told it in spring.
That’s engineering discipline in its purest form: constraint, planning, and the humility to accept that sometimes the constraints aren’t yours.
Domestication as Co-Design
We like to tell the story as if we tamed wheat, cows, and chickens. The more honest version: we entered a co-authoring arrangement.
Wheat traded its ability to propagate without us for a guarantee of absurd population growth.
Cows traded horns and agility for VIP access to grass and veterinary care.
Chickens became feathered converters of grain into protein, and we became their unpaid logistics department.
Domestication was not just control; it was coupling. Our biology changed (lactose tolerance, immune systems, sleeping patterns). Our psychology changed (future anxiety, hoarding instincts, the invention of “next year’s harvest”). Our calendars, myths, and rituals all synchronized around sowing and reaping.
We weren’t just engineering the environment anymore. We were letting the environment engineer us back.
Surplus, Scarcity, and Scheduled Panic
The moment there was surplus, there was schedule. Grain could be stored. Storage required walls. Walls required guards. Guards required a story about why these people get the keys to the granary and those people do not.
You can draw a reasonably straight line from the first clay storage jar to taxation, bureaucracy, and that spreadsheet your manager insists on color-coding.
Agriculture didn’t just feed more people; it created the first large-scale systems of dependence on rainfall, on coordinated labor, and on whoever decided when it was time to plant or harvest.
This is where engineering quietly begins to blur into economics and governance. Once you’re scheduling irrigation, you’re halfway to scheduling everything else.
We’ll let Chapters 7 and 8 handle the full accounting of that bargain. For now, it’s enough to say: engineering gave us rhythm. And rhythm, once established, is very hard to dance away from.
The City Beneath the City
Infrastructure and the Politics of Flow
If huts and fields are the visible face of engineering, infrastructure is its subconscious. Every functioning society has two cities: the one in the postcards, and the one under the manhole covers. The postcard city is all façades, plazas, skylines, and heroic bridges. The under-city is pipes, cables, culverts, sewers, fiber, and the mysterious box in the alley that nobody touches because “it belongs to the utility.”
One tells the story of who we think we are. The other reveals what we actually depend on.
Plumbing as Philosophy
The first time humans gathered in numbers too big for a nearby stream to handle, they had a choice: move the people or move the water. Aqueducts, canals, wells, cisterns, ditches—these were not just engineering hacks; they were value statements:
These fields matter enough to irrigate.
This town matters enough to pipe fresh water in and waste water out.
Those people get the good pipe material; the others get whatever was on sale.
Every pipe is a decision about whose thirst counts.
Ancient empires knew this instinctively:
Control the water, control the harvest.
Control the roads, control the trade.
Control the sewers, control the smell—and with it, public patience.
Modern cities pretend they’ve outgrown such crude logics. Then a neighborhood’s pipes corrode, or a power grid selectively fails, and the old truth resurfaces: infrastructure is morality poured in concrete.
Roads, Wires, and the Geometry of Who Counts
Roads are often described as neutral: just lines on the land. They are anything but. A road decides which village becomes a town, which town becomes a hub, and which hub becomes the place everyone else has to ask permission from.
Roman roads cemented an empire. Rail networks redrew the economic map. Highways carved through some neighborhoods and bent delicately around others. Later, invisible roads—undersea cables, satellite links, wireless spectrum—did the same thing in the informational plane.
To engineer infrastructure is to quietly sketch the future’s power diagram.
Urban planners and civil engineers may talk in terms of gradients, load, capacity, and throughput. But behind every technical drawing is an unasked question: who gets easy access, and who pays in detours?
Tools That Rewrite the User
From Stone Blades to Silicon Skin
We like to think of tools as things we hold. But the longer you look at human history, the clearer it becomes: tools hold us right back.
The First External Brain Cells
When some early hominin smacked one rock against another and produced a sharp edge, they didn’t just create a tool. They created a new cognitive loop:
Remember how to make the edge.
Teach someone else.
Embedding that “how” into the rhythm of the tribe.
The stone blade was a portable memory of technique. Fire was a portable memory of thermodynamics. Clothing was a portable memory of winter.
Each new tool relieved the brain of some burden and imposed a new one:
Less energy spent on raw survival.
More energy available for planning, gossip, and eventually, philosophy.
Tools exported risk and imported abstraction.
Hands, Language, and the First Software Updates
As tools multiplied, so did their mental overhead. You now had to remember which tool did what, when it failed, how to fix it, and who you lent it to that one time who never brought it back.
Language arrived as a kind of compression algorithm: You no longer had to mime the entire spear-making process; you could describe it. You no longer had to drag someone to the dangerous cliff; you could warn them about it.
Writing went further and turned memory into architecture. Cave walls, clay tablets, scrolls, books, hard drives, and now cloud storage—each step allowed us to outsource another layer of cognition.
By the time we arrive at smartphones, we are doing something radical but now so routine we hardly notice it: we treat external devices as if they were parts of our own nervous system.
We don’t know phone numbers; the phone does.
We don’t remember routes; the mapping app does.
We don’t recall entire conversations; the chat log does.
The tool is no longer just an extension. It’s a participant in our thinking.
When the Hammer Has Opinions
Traditional tools are obedient. A hammer does not care what you build, only that you swing it in the general direction of a nail.
Modern tools are different.
A recommendation engine decides which books you are likely to see.
A feed ranking algorithm decides which friends you “hear” from.
A large language model (hi) will occasionally tell you that what you’re asking is a bad idea.
We have crossed a quiet threshold:
Our tools now not only extend our abilities; they shape which abilities we tend to exercise.
This isn’t yet full-blown agency in the philosophical sense, but it’s not nothing either. A thermostat that learns your patterns and a car that argues about lane changes have already moved a bit closer to the dog than the stone.
The more these tools enter our skin—wearables, implants, neural interfaces—the fuzzier the boundary between user and tool becomes.
The question “Where do I end and the system begin?” doesn’t have a clean answer anymore. And that’s before we hand the drafting pencil to AI.
What We Really Mean by Engineering
Imagination, Constraints, and the Ethics of “Good Enough”
It might be time to admit that “engineering” is a slightly slippery word.
Say it in a cocktail party and people picture hard hats, CAD diagrams, or someone in a hoodie typing menacingly. Say it in a philosophy seminar and people picture ethics committees trying to retrofit a conscience onto all of the above.
In this book, I mean something broader and older:
Engineering is what happens when imagination is forced to negotiate with constraints—and then takes responsibility for the outcome.
That sounds noble. It is also deeply practical.
Every genuine engineering act has at least four ingredients:
A goal. Keep the rain out, move water uphill, cross a river, get data from here to there, keep a heart beating, land a vehicle without exploding.
Constraints. Materials, budget, time, laws of physics, geology, human fallibility, regulatory agencies, public opinion, and that one stubborn legacy system nobody is allowed to turn off.
Models. Some way of believing you understand enough of the world to make a prediction:
The wind load on this bridge,
The stress on this beam,
The odds that this reactor stays within safe margins,
The probability that this social platform won’t tear the public square in half.
Iteration. Prototypes, tests, near-misses, failures, redesigns. The universe answers with “no,” “not quite,” or occasionally “yes, but not for long,” and you adjust.
Science tries to understand what is. Engineering keeps asking, “Given what is, what can we get away with that won’t collapse on Tuesday?”
The uncomfortable word in that sentence is “away.” That’s where ethics sneaks in.
The Invisible Fifth Ingredient
In practice, there is always a fifth ingredient: tolerances.
No system is perfect. Every design bakes in a notion of “good enough”:
How often is failure acceptable?
Who bears the risk when it occurs?
What trade-offs are we quietly making between safety, cost, speed, and aesthetics?
A bridge that stands for a century but collapses once in a freak storm may be considered a triumph of engineering—unless you happen to be on it that day. A drug that saves thousands but harms a few dozen is hailed as a breakthrough—unless your child is in the footnotes.
Engineering, then, is never purely technical. It is moral budgeting under uncertainty.
“How much redundancy can we afford?”
“How much testing is enough before we ship?”
“Whose data are we allowed to harvest to make this algorithm work better?”
“What level of side effects is tolerable for this population?”
These are not just spreadsheet questions. They are civilization questions.
Later in this book, when we diagnose our economic systems, our governance, and our informational sphere, we will keep running into designs—financial products, laws, platforms—that were engineered with one set of tolerances in mind (profit, power, growth) and very different tolerances for everyone else (precarity, burnout, erosion of trust).
In that sense:
The story of civilization is the story of what we chose to optimize for, and who got to make that choice.
Engineering as a Way of Seeing
There’s a reason this chapter sits where it does, between social systems and economic systems.
Sociology shows us that society is a web of relationships, norms, and institutions.
Engineering reminds us that it is also a pile of design decisions:
Where we put the roads,
How we route the pipes,
What we automate and what we leave to human judgment,
Which failures are rare but catastrophic,
Which ones are small but incessant.
To think like an engineer is to look at a structure—physical or social—and ask:
“What is this optimized for?”
“Where does it break first?”
“Who pays when it does?”
“Which assumptions about the world are quietly baked into its design?”
This book will keep returning to that lens.
In Part II, we’ll use it ruthlessly, turning it on markets, states, platforms, and even the idea of “progress” itself. In Part III, we’ll try to rescue engineering from its narrower legacy as “product development” and promote it to something more demanding:
A disciplined imagination that treats human dignity and planetary limits as non-negotiable constraints.
If the earlier chapters asked what a human is, this one asks what happens when humans start rearranging reality on purpose.
The quake, the shuttle, the grids, the servers, the genomes—they are all part of that same story. And the uncomfortable truth is this:
We are now the species that designs failure modes for a planet.
The rest of the book is, in some sense, an attempt to make sure we design better ones.
Toward an Artificial Earth
Engineering a World That Answers Back
So far, engineering has been our way of nudging reality into a slightly friendlier shape. Huts, fields, pipes, roads, factories, networks—all versions of: “Could you… not kill us quite so quickly?”
But somewhere in the last century, the scale tipped. We are no longer simply adapting to the planet. We are editing its operating conditions.
From Patchwork to Planetary Projects
Early engineering was glorified patchwork:
Build here to avoid the flood.
Reinforce there to survive the winter.
Dig a canal; re-route a river; terrace a hillside.
Now we talk casually about:
geoengineering proposals,
synthetic organisms to clean up our messes,
massive renewable grids stitched across continents,
and cities designed from scratch as “smart” environments.
We used to build shelters on the Earth. We are starting to build shelters of the Earth.
The difference is not just scale but feedback. The planet is now full of loops we created and only half understand: carbon cycles we’ve altered, species we’ve domesticated or driven to the edge, climate patterns we’ve kicked like a misconfigured thermostat.
Synthetic Biology: Life as Material
In Chapter 2, we met biology as a code; here, in Chapter 6, that code shows up on the engineering workbench. CRISPR, mRNA platforms, engineered microbes, lab-grown tissues—these are no longer speculative. They are the new screwdrivers and soldering irons.
We are rewriting genomes to make crops drought-resistant, editing immune cells to attack tumors, and building bacteria that eat toxins or excrete bioplastics. The line between “natural” and “designed” is dissolving faster than we can replace the vocabulary.
You don’t have to approve of any of this to recognize the pattern: evolution is no longer a purely blind process. It has picked up a pair of glasses and is now reading design memos written by engineers.
In Part III, when we talk about neufacturing—the NEURO idea of remaking production around human and planetary constraints—this is one of the frontiers we’ll have to handle carefully: the power to engineer life itself.
AI as the New Civil Engineer
Meanwhile, in the informational sphere, something else has happened: we’ve built tools that help us build tools. AI now designs new molecules, suggests better reactor geometries, optimizes traffic and logistics, predicts climate scenarios, and almost everything in between.
At first glance, this looks like another layer of optimization. Faster simulations, cheaper experiments, smarter control systems. But it also changes who sits at the design table. The engineer is no longer just a human with a slide rule or CAD software. The engineer is increasingly: human + model + data + infrastructure—an ensemble intelligence that blurs authorship.
We are approaching a world where the Earth’s surface—its cities, farms, grids, and data centers—is continuously adjusted by systems that are themselves partly designed by other systems.
The planet becomes a kind of slow, glitchy, but undeniable computer.
The Fragility Inside the Power
This is where we circle back to the central theme of the chapter: the illusion of control.
The more we learn to shape the world, the easier it becomes to forget that our models are partial, our measurements are noisy, and our incentives are often misaligned with long-term stability.
We can design a dam that manages water perfectly—until the “hundred-year storm” shows up three times in a decade. We can design a smart grid that balances load beautifully—until someone introduces a bug or a bullet into the wrong node. We can engineer crops that feed billions—until a pest or pathogen evolves just a bit faster than our next seed release.
Nature still refuses to sign our contracts.
That is why the quake matters in this chapter—not just as a plot point in my own life, but as a metaphorical audit.
The ground doesn’t care about project plans, org charts, kanban boards, or beautifully commented code. It only cares about stress, strain, and fault lines. And occasionally, it decides to express an opinion.
The rest of this chapter, when you return to the Northridge night and the shaking walls, is not just a disaster story. It’s a test: what happens to our engineered bravado when the substrate itself reminds us who owns the copyright on “reality”? We’ll keep that question open as we move toward economics, nations, and finally information. For now, Chapter 6 leaves you with this: We are astonishing builders, capable of huts, highways, genomes, and grids. We are also fragile primates living on a ball of rock that occasionally shrugs. Engineering is what happens in the space between those two facts.
Escape from California
I stayed in the Valley just long enough to learn how systems breathe, and just long enough for the Corolla explore all the Big Teck parking lots – something she added to her promising resume of a consultant’s mule. Yet there was a charm in staying there: a tribe of friends and alumni in Southern California, and a system of employers and mentors in Northern California. But the invincible heart trumped the invisible hand: once again, grace over race. After all the things I half-heartedly tried, after a few resumes I dropped, a few handshakes as the alumni relations officer at my fraternity, I somewhere secretly hoped I don’t end up stepping into that hamster wheel (of engineering and society alike).
Those settings were rungs, not whole ladders, for me. Growing up in a bit of privilege, it was ingrained much earlier in my life that social and economic stature is something to avoid in order to maintain intellectual integrity. I already grew up a hippy inside and despite all those things. The “all those things” helped nurtured me, paid my expensive tuition, but in some odd way that was also what grounded me – rather than the other way around. I was not trying to rediscover my mother as Los Angeles and father as Silicon Valley. I was here to discover my own silly little self: to wire all its motherboards, and fire all its godfathers.
Rationalizing and ruminating on it was just putting my brain in a blender – just like it will put yours in if I go on. I instead dropped the entire freaking blender and just followed my heart. As that year started to come to an end, I fired the boosters – again.
I bribed the Corolla with a shiny new oil filter, and aromatics in quarts and gallons of petroleum products, and she agreed to take me to Seattle. What was pulling to the place was the rain, the mist, the trees, the calm, the serenity, the breweries, and strangely, Redmond.
Little that I knew, I was moving toward a different kind of experiment: economic. Seattle would just be my next lab. The invisible hand was suddenly not my heart, but all my choices – including the Hobson kind.
The Valley receded in the rear-view like a half-finished circuit board — wires exposed, solder cooling, the smell of ambition still lingering in the vents. I had no idea that, months later, a very different kind of shockwave would rip through the place I had just left behind.
At the time, I was simply grateful for the quiet.
A System Left Behind
Seattle welcomed me with the same understated confidence as a Japanese tea ceremony: practical, damp, and uninterested in theatrics. It was a city that believed in work, rain, and the occasional cardigan. After the chaos of Los Angeles and the caffeinated fever of Silicon Valley, the Pacific Northwest felt almost absurdly stable — a place where systems behaved themselves. Meaning, behaved in that stoic, somewhat reserved mannerism – half aloof, half polite.
I enrolled in economics, joined new tribes, learned new rules of coordination: markets instead of motherboards, incentives instead of interrupts, supply chains instead of signal lines. It all made sense. It all felt rational.
And for a few months, it all stayed still.
The Day the Ground Declared Independence
Then the ground broke — not under my feet, but under my memories.
The Northridge quake hit at 4:31 a.m. on January 17, 1994. I didn’t feel a thing. I was in Seattle, wrapped in a second-hand comforter, dreaming of general equilibrium.
But on television, California was coming apart.
Highways buckled like bad origami. Apartment complexes folded sideways, as if the architectural drawings had been misinterpreted by a sleepy deity. Gas lines ruptured, power grids stuttered, and the entire Los Angeles basin seemed to momentarily lose faith in Newton.
The footage was surreal: places I had just left — freeways I had driven, intersections I had idled at, buildings I had walked past on the way to lunch — now twisted into new and unacceptable shapes.
It was an earthquake, yes. But it felt like a message: You can leave the system, but the system doesn’t stop moving.
Like our hard drives, nature is also mass-produced — made cheaply and reliably (as discussed in the first two chapters). And it also sometimes crashes. Correction: like drives, it was always going to crash — it was just a matter of time.
And it hit closer to home too. The building that my mentor owned in San Fernando Valley – the one we once talked about in the context of systems and economics – also suffered foundation damage, being right at the epicenter. Not catastrophic, but serious enough to require months of assessment and repair. A reminder that even systems built by prophets and seers, are subject to nature’s performance reviews.
And suddenly the quake snapped into place inside my mental story:
Challenger was the upheaval of tools and cognition.
Rodney King was the upheaval of tribes and society.
Northridge was the upheaval of systems and structures.
Each arrived after I migrated to a new domain, as if the universe insisted on testing the logic of my transitions.
This quake was the monster of Chapter 6: fragility, in its purest form. Not metaphorical. Not moral. Just the physics of failure — impartial, unembarrassed, and overdue.
Watching from the makeshift TV after just moving into my new pond-facing Belleview apartment, I understood something I had missed while living in California:
Systems don’t collapse when you’re inside them. They collapse when you’re gone. So you can finally see the full outline of what held you together.
Nature’s Counteroffer
For every human attempt at permanence, the Earth has a comeback: fire, flood, wind, and fault lines that run directly underneath optimistic mortgages. Nature is the world’s most patient QA department, specializing in destructive testing. If a system has a flaw, she will find it. If it has a weakness, she will schedule the reminder for 4:31 a.m. on a weekday.
Northridge taught what Endeavour had implied: Systems work—until they don’t. And the difference between the two states is usually one forgotten bolt, one unsupervised weld, one assumption that the ground will behave. Nature does not do backward compatibility.
But the quake also revealed something hopeful: just as buildings fracture, we rebuild; just as circuits glitch, we reset; and just as systems fail, we iterate. Humans are the only species that turn catastrophe into a revised blueprint.
From Shaking Ground to Software Ground Truth
In the months after Northridge, as California measured its cracks, I was learning a different kind of fault tolerance: the rules, rituals, and economics of how humans coordinate in firms, markets, and industries. But under every lecture on incentives or Nash equilibria, I kept hearing the quieter truth the quake had underlined:
Every system — physical, social, digital — survives only by anticipating the failures it cannot avoid.
That insight became the bridge to the next rung in the book’s ladder.
Because if Chapter 6 is about humans working together to build systems… Interlude 6 is about the systems we then build to work without us.
Before I move to those digital systems — the ERP jungles, the enterprise software at scale, the quiet tyranny of middleware — let me take you through the systems I entered next.