Features

Code Blue

Code Blue: October 2013: The President's health care web is in cardiac arrest, threatening to to drag his signature initiative down with it. Enter Mikey Dickerson '01...

code-blue-600Lunch was supposed to be casual. Mikey Dickerson ’01 was in Chicago catching up with Dan Wagner, a friend who’d been in the trenches with him on Barack Obama’s campaign for the presidency in 2012. Wagner had since gone on to found a company, Civis Analytics; Dickerson was a site reliability engineer at Google, one of the people who make sure that the search engine never, ever breaks down.

This was October of 2013, no time for the President’s geekiest loyalists to have a little fun. Healthcare.gov, the sign-up website that was the signature element of President Obama’s signature initiative, was a technological disaster. People couldn’t sign up even if they wanted to—the site would break, or fail. Delays were interminable. Information got lost. Customer service was about as good as you’d expect from a cable TV company. The Department of Health and Human Services, responsible for the new health care system, couldn’t seem to get it working.

“So, we got this phone call yesterday,” Wagner told Dickerson. “HHS is looking for help with healthcare.gov. Can I list you as an advisor or consultant?”

“Yeah, sure. If it’s any value to you, list me,” Dickerson replied. It seemed innocuous enough. Today, he smiles at his own naïveté. “I had no idea what I was getting into,” he says. About a week later, Dickerson found himself on a 5 a.m. conference call with a van full of technologists in Washington D.C., headed over to HHS. With him in the White House motor-pool car was Todd Park, the U.S. chief technology officer. And Park, whom Dickerson didn’t know, was selling the group as a team of experts who could solve any tech problem. Dickerson realized: They’re saying I can fix healthcare.gov.

Without really meaning to, Dickerson had become an anchor of the Obama administration’s “tech surge,” a Silicon Valley-powered push to fix the bugs in the healthcare.gov system. But the system was more than just software. In D.C., Dickerson and his new team found an organization in bureaucratic and technological meltdown, unable to execute what any e-commerce start-up would consider basic prerequisites for being in business.

The crazy part is, they fixed it.

To a Connecticut native like Dickerson, good at math and computers but with no desire to attend a big university, Pomona shows itself off pretty well—especially on a campus visit in May, when Dartmouth might still have slush on the ground. It’s not that he was so avid about computer science—in those days, as a major, CS really ran out of Harvey Mudd anyway—it’s just that Dickerson was an ace. He felt like he was cheating just a little. “It seemed dumb to be spending all that money on something I was already good at,” he says. In fact, Dickerson was already coding for various companies while in school. After graduation, he ended up working in Pomona’s computer lab.

Then the 2000 presidential election came around, with its photo finish in favor of George W. Bush. “It was a trauma for me,” Dickerson says. “That razor’s edge. All that was intensely painful. Almost anything would have moved those last 200 votes.” So in 2004 Dickerson volunteered with a poll-watching group … and caught the politics bug. Four years later he was working at Google, where CEO Eric Schmidt was (and remains) a multimillion-dollar Obama supporter. During campaign season an email went to a mass-distribution list that Dickerson was on, looking for people who could manage big databases for the Obama campaign.

Hey, Dickerson thought. I manage a group that runs large databases. And that was it. He worked as a volunteer in Chicago, one of a small group of techies who, during their long nights, idly wondered if maybe they could do something useful for the campaign with better records of people’s voting history. When the 2012 campaign came around, he was still on the campaign organizers’ list. This time, though, he was no newbie—though still technically a volunteer, his experience made him a trusted veteran. Those vague ideas about leveraging voter lists went into practice, and Dickerson’s group became the analytics team, credited by some political analysts as having been the key to Obama’s re-election. Once the campaign was over, Dickerson went back to managing a site reliability engineering team at Google, but he stayed in touch with his friends—which is why Dickerson was at lunch with Wagner on October 11.

The tech team’s first stop, in Virginia on October 17, was PowerPoint Hell. Technically, it was a large IT firm working as a government contractor. “They scheduled a three-hour meeting and sent a VP with, I shit you not, a 130-slide PowerPoint presentation,” Dickerson says. Over beers in a bar on San Francisco’s Embarcadero, about a block from Google’s offices, Dickerson wears the uniform of the coder—hoodie, Google ID badge, Google T-shirt, close-cropped hair and unshaven chin. In San Francisco, that’s stealth armor. In Washington’s blue-sports-coated, khaki-pantsed hallways, he was an alien.

The group fought its way out of the meeting and took over the office of someone who was on vacation. Then they went wandering, finding teams huddled in cubicles and asking them what they were working on, which bugs they were trying to fix. But they weren’t—mostly they were waiting for instructions. In their defense, it was hard to figure out what needed fixing. Engineers weren’t really allowed to talk to clients or users, and the people who created the healthcare.gov website hadn’t even built a dashboard, a way to monitor the health and status of their own system. If you wanted to know whether healthcare.gov was functioning, the only way to find out was to try to log on. “We thought this would be a targeted assessment and we’d spend a few days there,” says Paul Smith, another member of the team. “When we realized how bad things were, we just independently decided, we’re not going home. This is what we’re doing now, for an indefinite period of time, until it gets better.”

After a couple of days, Park asked them whether it could be fixed. “Todd, they have made all the mistakes that can be made,” Dickerson told him. “We can barely find a case where, when two decisions could be made, they made the right one. But low-hanging fruit isn’t the right metaphor. We’re stepping on the fruit.” The point was, some very simple fixes would yield some very big gains. Any improvement would be a massive improvement. Google site reliability engineers have a saying—they tell each other, if we have an outage that big it’ll be on the front page of The New York Times. Is that what you want? “But here’s the thing,” says Dickerson. “Healthcare.gov had been on the front page of The New York Times for four weeks. That was the silver lining. How much more could I screw it up?”

The group of coders decided that if no one was telling anyone what to do, they would. That’s when they started getting called “the Ad Hoc Team.” The name stuck. “We had a big stick, because we were the magical guys from the White House,” Dickerson says. “After a couple of days, we instituted a war room.” Every morning at 10 a.m., every team had to send a representative to a big meeting to explain what was going right, or wrong, and why. “It was an incredibly expensive thing to do—60 people in a room while we arbitrate disputes between two of them. But we made so much progress we stopped worrying,” Dickerson says. “Having a giant studio audience is better sometimes. It’s harder to say, ‘I didn’t do that because it wasn’t on my task order.’”

In other words, Dickerson had built into the system something no one had thought of: accountability. “What Mikey really excelled at was, if there’s a priority issue that needs to be addressed, how can people address it? What do they know? What do they need to know? What’s blocking them?” says Smith. “That’s just his demeanor and the way he operates.” The meetings were so productive and making so much of a difference in site performance that the Ad Hoc Team instituted a second one, making them twice a day, seven days a week.

When they weren’t in the war room, they coded. Problems started getting solved. A stupid little flaw that required the same kind of wait to connect to the database every time went away with the change of a couple of configuration settings, and poof! An eight-second response delay dropped to a two-second delay. “And that’s still terrible,” Dickerson says. The site stopped crashing. People actually started signing up for health care.

The work took a toll, though. Except for a quick trip back to California to pick up some clothes—Dickerson had come to the East Coast with a carry-on bag and a Google computer, expecting a short visit—he was in the greater D.C. area from mid-October through Christmas. Dickerson estimated he ran 150 war-room meetings in a row.

After a couple of moves to accommodate bureaucracy, Dickerson ended up working remotely, alone, from an operations center in Columbia, Md.—three hours from D.C. in what locals sometimes call “spook valley” for its preponderance of government contractors. Since healthcare.gov’s original creators hadn’t built a ship-in-a-bottle version of the software to test updates and fixes, everything the Ad Hoc Team fixed had to get changed on the live site, and the primary maintenance window was when traffic was lightest, between 1 and 5 a.m. “It was literally 20-hour days a lot of time. ” Dickerson says. “I was hallucinating by the end, hearing things.”

mikey-400With 12 days left before the deadline, Dickerson was ready to go home. He gave a speech listing the five mission-critical things remaining, and attempted to flee back to California. But the bosses panicked. The Ad Hoc guys can’t go home, they said. They gave him the service-to-your-country pitch. They begged. So Dickerson agreed to stay through to the end—with some conditions. He got to set the specific technical goals for what his team and the rest of the government coders would do. And he got to hire whomever he wanted, without arguing the point. He wanted to be able to trust the new team members, so he chose them himself. Eventually a rotating team of Google site reliability engineers started coming through to keep the project on track.

Dickerson got to dictate those terms because he was getting results. He had become indispensable. “Mikey is an incredible talent who was seemingly built in a lab to help fix healthcare.gov,” Park says. “It’s not just the fact that he’s got a sky-high tech IQ, honed over years as a star site reliability engineering leader. He’s also got tremendous EQ, enabling him to step into a tough situation, mesh well with others, and help rally them to the job at hand.”

The real bummer, of course, is that healthcare.gov, while an unprecedented attempt to link government services, private insurers and identity verification, shouldn’t have been that hard to build. “It’s basically a distributed, transactional, retail-type website, and we’ve been building those for years,” says Smith. “In the private sector, we know how to do that. We’re not forging new computer science ground here, right?”

By April of 2014, just a few days after Dickerson and I spoke, the Obama administration announced that over 7 million people had signed up for private health care through federal and state exchanges, and 3 million had signed up for Medicare. The program had made its numbers—barely, to be sure—because people, in the end, could actually use the website.

Dickerson is back at Google, but as he says, “you can never unsee the things you see in the federal government.” He has become an outspoken advocate for reform in the ways government builds technology, concentrating especially on trying to convince young technologists to go work for government. “You’re gonna eat free food and drink free soda in micro-kitchens and work on another version of what we’ll say, for argument’s sake, lets people share pictures of what they ate for breakfast, and tens of thousands of people will die of leukemia because we couldn’t get a website to work,” Dickerson says. “These are real people’s lives that will end in 2014, and you’re going to sit at your desk working on picture sharing.”

The problem isn’t competence. People who work on websites for the government are every bit as competent as the ones who work at Google or Facebook. “The mechanisms by which you do a contract with the federal government are so complex that it requires expertise in and of itself,” says Jennifer Pahlka, founder and executive director of Code for America, a group that connects software developers with local governments. “Fundamentally the process in government has evolved to meet government needs. A federal project has dozens of stakeholders, none of whom represent the user.”

That’s why Code for America focuses on local governments, Pahlka says. The feds are too hard to crack, and anyway, most people’s interactions with government are at the state and city level—think DMV, local parks, or trash pick-up. So Dickerson has started stumping for Code for America, giving speeches at their events. And he is lobbying Eric Schmidt and his other bosses at Google to develop programs that would allow—maybe even encourage—software developers there to take time to work on government projects. Consider: The feds paid $700 million for healthcare.gov, and it didn’t work. Imagine being able to bid for that contract at a tenth the price. “I don’t have to appeal to your altruism or desire to serve your country,” Dickerson says. “I can just say, ‘Do you want to make a ton of money?”

Pahlka thinks the pitch might actually work—and not just because of capitalism. “The consumer internet has influenced the way a generation feels about doing things together,” she says. “You have a generation of people who value collective intelligence and collective will—not necessarily collective political will, but the ability to actually do things together.” Software designers and engineers are already political, Pahlka and Dickerson are saying; it’s just that the web generation is ignoring the greater good. Going to work at Twitter is a political choice just as much as going to work for the Department of Veterans Affairs.

“I give the worst sales pitch,” Dickerson says. “I tell people, ‘This is what your world is going to be like: It’s a website that is a Lovecraft horror. They made every possible mistake at every possible layer. But if you succeed, you will save the lives of thousands of people.’”

The weird part: Almost everyone says yes.

————-

EDITOR’S NOTE: Shortly before this magazine went to press, Dickerson announced that he’s going to practice what he preaches, full time. He is leaving Google to join the Obama administration as administrator of the U.S. Digital Service, a newly created office overseeing government spending on information technology. And after signing on, he discovered that the lead designer on the initial staff for U.S.D.S. is another Pomona grad, Mollie Ruskin ’08.

The Code of Beauty, the Beauty of Code

Class Program
{
public static void Main()
{
System.Console.WriteLine(  “Hello, world!”  );
}
}

Even if you’re the kind of person who tells new acquaintances at dinner parties that you hate email and e-books, you probably recognize the words above as being some kind of computer code. You may even be able to work out, more or less, what this little ‘program’ does: it writes to the console of some system the line ‘Hello, world!’

hackers-300A geek hunched over a laptop tapping frantically at the keyboard, neon-bright lines of green code sliding up the screen—the programmer at work is now a familiar staple of popular entertainment. The clipped shorthand and digits of programming languages are familiar even to civilians, if only as runic incantations charged with world-changing power. Computing has transformed all our lives, but the processes and cultures that produce software remain largely opaque, alien, unknown. This is certainly true within my own professional community of fiction writers—whenever I tell one of my fellow authors that I supported myself through the writing of my first novel by working as a programmer and a computer consultant, I evoke a response that mixes bemusement, bafflement and a touch of awe, as if I’d just said that I could levitate. Most of the artists I know—painters, film-makers, actors, poets —seem to regard programming as an esoteric scientific discipline; they are keenly aware of its cultural mystique, envious of its potential profitability, and eager to extract metaphors, imagery and dramatic possibility from its history, but coding may as well be nuclear physics as far as relevance to their own daily practice is concerned.

Many programmers, on the other hand, regard themselves as artists. Since programmers create complex objects and care not just about function but also about beauty, they are just like painters and sculptors. The best-known assertion of this notion is the essay ‘Hackers and Painters’ by programmer and venture capitalist Paul Graham. ‘What hackers and painters have in common is that they’re both makers. Along with composers, architects and writers, what hackers and painters are trying to do is make good things.’

According to Graham, the iterative processes of programming—write, debug (discover and remove bugs, which are coding errors, mistakes), rewrite, experiment, debug, rewrite—exactly duplicate the methods of artists: ‘The way to create something beautiful is often to make subtle tweaks to something that already exists, or to combine existing ideas in a slightly new way … You should figure out programs as you’re writing them, just as writers and painters and architects do.’ Attention to detail further marks good hackers with artist-like passion:

All those unseen details [in a Leonardo da Vinci painting] combine to produce something that’s just stunning, like a thousand barely audible voices all singing in tune. Great software, likewise, requires a fanatical devotion to beauty. If you look inside good software, you find that parts no one is ever supposed to see are beautiful too.

This desire to equate art and programming has a lengthy pedigree. In 1972, the famed computer scientist Butler Lampson published an editorial titled ‘Programmers as Authors’ which began:

Creative endeavor varies greatly in the amount of overhead (i.e. money, manpower and organization) associated with a project which calls for a given amount of creative work. At one extreme is the activity of an aircraft designer, at the other that of a poet. The art of programming currently falls much closer to the former than the latter. I believe, however, that this situation is likely to change considerably in the next decade.

Lampson’s argument was that hardware would become so cheap that ‘almost everyone who uses a pencil will use a computer,’ and that these users would be able to use ‘reliable software components’ to put together complex programs. ‘As a result, millions of people will write non-trivial programs, and hundreds of thousands will try to sell them.’

hackers-250A poet, however, might wonder why Lampson would place poetry making on the same spectrum of complexity as aircraft design, how the two disciplines—besides being ‘creative’—are in any way similar. After all, if Lampson’s intent is to point towards the future reduction of technological overhead and the democratization of programming, there are plenty of other technical and scientific fields in which the employment of pencil and paper by individuals might produce substantial results. Architecture, perhaps, or carpentry, or mathematics. One thinks of Einstein in the patent office at Bern. But even the title of Lampson’s essay hints at a desire for kinship with writers, an identification that aligns what programmers and authors do and makes them—somehow, eventually—the same.

Both writers and programmers struggle with language. The code at the beginning of this chapter is in Microsoft’s C#, one of thousands of high-level programming languages invented over the last century.

Each of these is a ‘formal language,’ a language ‘with explicit and precise rules for its syntax and semantics,’ as the Oxford Dictionary of Computing puts it. Formal languages ‘contrast with natural languages such as English whose rules, evolving as they do with use, fall short of being either a complete or a precise definition of the syntax, much less the semantics, of the language.’ So these formal dialects may be less flexible and less forgiving of ambiguity than natural languages, but coders—like poets—manipulate linguistic structures and tropes, search for expressivity and clarity. While a piece of code may pass instructions to a computer, its real audience, its readers, are the programmers who will add features and remove bugs in the days and years after the code is first created. Donald Knuth is the author of the revered magnum opus on computer algorithms and data structure, The Art of Computer Programming. Volume 3 of the Art was published in 1973; the first part of Volume 4 appeared in 2011; the next part is ‘under preparation.’ If ever there was a person who fluently spoke the native idiom of machines, it is Knuth, computing’s greatest living sage. More than anyone else, he understands the paradox that programmers write code for other humans, not for machines: ‘Let us change our traditional attitude to the construction of programs: Instead of imagining that our main task is to instruct a computer what to do, let us concentrate rather on explaining to human beings what we want a computer to do.’ In 1984, therefore, he famously formalized the notion of ‘literate programming’:

The practitioner of literate programming can be regarded as an essayist, whose main concern is with exposition and excellence of style. Such an author, with thesaurus in hand, chooses the names of variables carefully and explains what each variable means. He or she strives for a program that is comprehensible because its concepts have been introduced in an order that is best for human understanding, using a mixture of formal and informal methods that reinforce each other.  

Good code, then, is marked by qualities that go beyond the purely practical; like equations in physics and mathematics, code can aspire to elegance. Knuth remarked about the code of a compiler that it was ‘plodding and excruciating to read, because it just didn’t possess any wit whatsoever. It got the job done, but its use of the computer was very disappointing.’

To get the job done—a novice may imagine that this is what code is supposed to do. Code is, after all, a series of commands issued to a dumb hunk of metal and silicon and plastic animated by electricity. What more could you want it to do, to be? Knuth answers: code must be ‘absolutely beautiful.’ He once said about a program called SOAP (Symbolic Optimal Assembly Program) that ‘reading it was like hearing a symphony, because every instruction was sort of doing two things and everything came together gracefully.’

We are now unmistakably in the realm of human perception, taste and pleasure, and therefore of aesthetics. Can code itself—as opposed to the programs that are constructed with code—be beautiful? Programmers certainly think so. Greg Wilson, the editor of Beautiful Code, an anthology of essays by programmers about ‘the most beautiful piece of code they knew,’ writes in his forward to that book:

I got my first job as a programmer in the summer of 1982. Two weeks after I started, one of the system administrators loaned me Kernighan and Plauger’s The Elements of Programming Style … and Wirth’s Algorithms + Data Structures = Programs. … [These books] were a revelation—for the first time, I saw that programs could be more than just instructions for computers. They could be as elegant as well-made kitchen cabinets, as graceful as a suspension bridge, or as eloquent as one of George Orwell’s essays.

Knuth himself is careful to limit the scope of his aesthetic claims: ‘I do think issues of style do come through and make certain programs a genuine pleasure to read. Probably not, however, to the extent that they would give me any transcendental emotions.’ But in the many discussions that programmers have about craftsmanship, elegance and beauty, there is an unmistakable tendency to assert—as Wilson does—that code is as ‘eloquent’ as literature. …

The day that millions will dash off beautiful programs—as easily as with a pencil—still remains distant. The ‘lovely gems and brilliant coups’ of coding remain hidden and largely incomprehensible to outsiders. But the beauty that programmers pursue leads to their own happiness, and—not incidentally—to the robustness of the systems they create, so the aesthetics of code impact your life more than you know.

This excerpt from Geek Sublime: The Beauty of Code, the Code of Beauty (Graywolf Press), by Vikram Chandra ’84, is published with permission of the author. In his first venture into nonfiction, the noted novelist roams from logic gates to the writings of 11th-century Indian philosopher Abhinavagupta, in search of connections between the worlds of art and technology.

Photos accompanying this excerpt are from the Spring 2014 Hackathon held at Pomona College and are by John Lucas.

The Island of California

The Island of California: Examine the original 17- and 18th century maps of the New World at Honnold-Mudd Library and you'll find an array of creative geography. But there's one point on which all seem to be in agreement: California was an island.

 

1600s map of California from Honnold-Mudd Library Special Collections.

1600s map of California from Honnold-Mudd Library Special Collections.

Somehow it seems fitting that the story of California should begin with a fabulous tale about a mythical island.

Both the island and the myth, along with the state’s future name, seem to have sprung first from the pen of Spanish writer Garci Ordóñez de Montalvo, whose lavish romantic novel Las Sergas de Esplandián (The Deeds of Esplandián), published around 1510, described a race of griffin-riding Amazons living in a far-off realm rich in gold and precious stones—“an island on the right hand of the Indies … very close to the side of the Terrestrial Paradise.” He dubbed this imaginary isle California, a name that may have been constructed from Latin roots meaning “hot oven.”

So, right from the start, California was portrayed as isolated, rich, strange, adventurous, bigger than life, sunburned and next door to Paradise. Is this starting to sound familiar?

The real California—the Baja part—was first discovered by Europeans in 1533 by an expedition commissioned by Hernán Cortés, the Spanish conqueror of Mexico. Sailing west from the Mexican mainland, the crew set ashore on what they believed to be an island. After their shore party was slain in a clash with the inhabitants, the survivors returned to the mainland with tales of an island full of pearls and other riches.

No one knows exactly when or where place and name actually came together, but at some point in the ensuing years of failed colonization, someone—probably some conquistador familiar with Montalvo’s tale and eager to believe in its treasures—gave the presumed island its suitably mythic name.

Here’s where things get a bit strange. Through the rest of the 1500s and early 1600s, the few surviving maps depicted the west coast of North America as a continuous line and Baja California as a peninsula. Then, in the early 1600s, the supposed island of California suddenly returned to the scene, apparently firing the imagination of mapmakers across Europe. For more than a century thereafter, California would be depicted as a huge, rugged outline separated from the west coast of the North American mainland by a narrow strait.

Perhaps the most intriguing thing about maps from this period is that the truth was already known by the time they were made. As early as 1539, one of Cortés’s lieutenants, Francisco de Ulloa, sailed north and confirmed that the so-called island was actually a peninsula, and by the mid-1600s, the geographic facts of the place had been pretty clearly established by its Spanish masters. So why did the island of California resist reattachment to the mainland for so long?

One practical reason may be that the people most familiar with the actual place weren’t making the maps. In the 16th and 17th centuries, the Spanish held sway over much of western North America. Most of the surviving maps from this period, however, were drawn by cartographers in Venice, Paris, Amsterdam and London. These maps were meant for public consumption, so they needed to appeal to the romantic notions of the time. Meanwhile, Spanish mapmakers were drawing their maps behind closed doors to be used by actual navigators, and Spanish officials, jealous of their secrets and worried about foreign intrusions into their New World possessions, had good reason to keep them under wraps—or even to encourage misinformation.

Historian Dora Beale Polk blames the voyage of the famous English explorer (and gentleman pirate) Sir Francis Drake into Pacific waters in 1578 for the myth’s 17th-century revival. Confused stories about Drake’s exploits along the west coast shores seem to have lent new strength to the notion that there was a continuous strait separating those lands from the continent.

But by the beginning of the 18th century, the only remaining prop for this geographical blunder seems to have been the persistence of myth. Mapmakers who should have known better still clung to the diminishing evidence that California was an island. Perhaps they were so enthralled by the notion of California as a strange and magical place—a place that simply felt more suitable as an island—that they couldn’t bring themselves to accept the more pedestrian truth.

A lot has changed, of course, since those maps were made. The California of the 1600s was eventually subdivided into three huge, modern states, one north of the border and two south of it. Here in the United States, the 31st state became the biggest, most populous, most diverse, and, in many ways, most controversial state in the Union.

And yet, as a metaphor, the island of California still feels eerily appropriate, even today. Maybe because there’s so much truth in it. After all, as a bio-region, California has been termed an “island on the land,” isolated from the rest of the continent by such natural barriers as deserts and mountain ranges. And from an economic standpoint, the state is frequently described as if it were a separate nation. (With last year’s economic surge, California reportedly regained its theoretical place as the eighth largest national economy in the world, just behind the United Kingdom and Brazil and just ahead of Russia and Italy.)

Perhaps most importantly, California continues to occupy a place in the cultural life of our nation that sets it apart. Admired by some as a place of innovation and a harbinger of national change and decried by others as a narcotic in the body politic, intoxicating the rest of the country with its crazy ideas, the state seems to inspire in Middle America just about every emotion except apathy.

In 1747, Ferdinand VI of Spain issued a royal proclamation declaring: “California is not an island.” That may have helped bring an end to the literal vision of California as an enchanted isle, but the idea of California as a quasi-myth—a strange and wonderful place in the distant west where venturesome souls might go to find adventure or wealth or simply a spot in the sun—was just getting started.

 

The California We Came To

Sometimes I wonder how it would have gone if this country had been settled backwards, west to east—if those doughty Pilgrims, huddled praying among the ship’s creaking timbers, had anchored not in the crook of Cape Cod but, say, in San Diego Bay. Would the relentless push that drove us westward have driven us eastward just as fast? Would the Eastern Seaboard have seemed as manifestly destined as the West Coast (which somehow never seems like a “seaboard”) once did? What would all that light and warmth have done to the iron in the Puritan soul? Would the Atlantic states—coming late into our consciousness—have seemed enchanted?

yosemite1a As it is, things have worked out nicely. California’s climactic geography came last, a necessary if unanticipated coda to what is often called the American experience. Knowing the end of the story—so far— makes it easy to grasp how incomplete this country would have felt without California, the volatile edge, it seems, of all our national imaginings. For much of the way westward, the story was about settling down, finding a homestead and improving it. But California was never really about settling down. Its very geology is transient. This is where you file a claim on the future and hope that events don’t overtake you.

 It’s hard to live in the everyday way and sustain a mythic consciousness. That’s what I learned going to high school and college in California. My family had crossed into the state over the Sierras, sluiced down 80 into Sacramento. In California, I expected to find a transubstantiated landscape glimmering with intimations of Pacific immortality, and I expected to be transubstantiated in turn. What can I say? We had come from Iowa, and I was 14, an age when the mere house-ness of the house we chose to live in and the car-ness of the car we drove seemed strangely disappointing. I hadn’t expected to find so much ordinariness on display. It seemed as though the Californians who already lived here had lost the magical sense that they were in California. And then I lost it too. It faded away like the San Gabriel Mountains after a hot autumn week without a breeze.

 None of us would get much done if we regularly inhabited a mythic consciousness, and the traffic would be so much worse. So much of life seems to require an ordinary perspective, the sameness and familiarity of the normal. There are times when Southern California seems like a vast machine engineered to produce endless quantities of the ordinary. And yet, from time to time, California rises up and smites you, and you find yourself re-dazzled. It may be the sun sinking out at the end of the 10—the “subtropical twilights,” as Joan Didion put it—or a day of purifying desert light. It may be chimney-stacks swaying slightly in a minor earthquake or the sight of the kelp-matted inshore, out beyond which the gray whales move. It may be nothing more than the scent of rain on asphalt in a dry winter. It hardly matters what it is. You look up, look around, and see, again, what an extreme and beautiful place this is, where the continent crumbles and slips and subducts and the weather blows in from the Pacific and the mountains seem like a temporary arrangement, just waiting to slide down into the Inland Empire.

 Over the past decade, I’ve come to Claremont and Pomona College every couple of years to teach. I always drive out from my home in New York because I always want to come into California from the great emptiness of Arizona or Nevada. It’s a strange sensation, familiar to nearly everyone who comes this way. You seem to get farther and farther west—to get more and more western—and then you cross into California and the very meaning of “west” changes. You have to look pretty hard to find the “west” in California that’s continuous with the west in, say, Elko, Nevada. But that’s one reason I like California so much—I keep discovering ways in which it’s discontinuous with anywhere else, discontinuous perhaps especially with itself.

  I settle in and remember what January smells like in Southern California. The place I left seems unimaginable, part of an old world that seems to contain everything but California. And I wonder again how it would have gone if it had all gone differently. What we have now are the myths that arise historically from the California we came to, not the California we came from. That makes all the difference, as the Pilgrims discovered in their own way and on their own coast.

January 2014

A Simple Prescription

A Simple Prescription: Dr. Juan Guerra '85 has a simple prescription for Latino health care: More Latino doctors.

guerra3

Children are always asked what they want to be when they grow up. As far back as he can remember, Juan Jose Guerra ’85 always had the same answer. He wanted to be a doctor. But unlike other boys who grow out of fantasies of being firemen or Air Force pilots, Guerra never let go of his goal. He forged ahead despite his immigrant background, his parents’ modest means, his lackluster test scores and the skeptical advisors who doubted he had the mettle for medicine. He persisted even after “crash-landing” through freshman chemistry at Pomona College and getting a D+ in biology, forcing him to switch majors from pre-med to economics.

You might say Guerra made an end-run around what he considers the brutal “weed-out system” of traditional pre-med. He took encouragement from professors outside of the sciences. He took summer courses at Georgetown to complete pre-med requirements. And he took time for a year of post-baccalaureate work at UC Irvine to help him boost his score on the MCAT, the medical school entrance exam, which he fumbled the first time around.

After all that, he was put on waiting lists for medical schools in California. In an admissions interview, one dean asked why he wanted to be a doctor, but arrogantly rejected the answer when Guerra said it was to serve his community. Finally, he found a spot in the urban health program at the University of Illinois College of Medicine, in Champaign-Urbana, which had fostered diversity in the field since the early ’70s, when Guerra was still a boy translating for his Salvadoran grandparents at their doctor’s visits.

By the time he graduated in 1993 with that hard-fought diploma in hand, it was like scoring a last-minute touchdown for the underdog team at the Super Bowl. “I think if it were an end-zone celebration, the referees would have thrown flags,” jokes Guerra, whose other outsized dream was to be a basketball player, despite his soccer-size stature. “For me, the future was just so vivid as a physician. That’s all I could see myself doing.”

Yet, even after all these years, he wonders why so many minority students in similar circumstances still don’t go the distance. “I don’t have an answer,” says Guerra. “Each person has a different reason for why they let go of their dreams. The journey to become a physician—to become anything—is different for many people. I was weeded out after getting that D+. I was told that was the end of the story. But in reality, it was just the beginning.”

Guerra didn’t really do an end-zone dance at his graduation. He seems too reserved for that. The young doctor simply went to dinner with his parents, then packed his bags and headed back to California to start his residency at Kaiser Permanente’s flagship hospital in Oakland, a city with a high population of Latinos. Guerra still works there today, leading an experimental program that he helped create to address the health care needs of Spanish-speaking patients. Named Salud en Español (Health In Spanish), the small clinic features an interdisciplinary approach to treatment, housing a team of 14 doctors, including family practioners as well as specialists in internal medicine, pediatrics and obstetrics/gynecology, Guerra’s chosen field. He likes to call the clinic “a medical home for our Latino members.”

Guerra’s fourth-floor office is located in a gritty urban neighborhood near the intersection of two freeways. It overlooks the outdated hospital where he started his career, and which is now being replaced by a modern facility. But not just the buildings are changing. The profession itself is being revolutionized, with use of digital case files, the advent of “Obamacare” and the pressure on doctors to produce measurable outcomes. That simply means they must prove that their patients are getting better, which he argues is one of the biggest benefits of culturally competent care.

But as he walks past that old hospital building, with its dreary Soviet-like architecture, Guerra often reflects on the things that haven’t changed in his chosen occupation. Society is still struggling to produce more physicians from underrepresented minorities, especially Latinos and African-Americans. In that respect, medicine is much the same as it was when he started 20 years ago.

Today in California, fewer than five percent of doctors are Latino, though Latinos constitute a third of the state’s population and half of the children born here. That sends the crucial doctor-to-patient ratio completely out of whack, according to the Sacramento-based Latino Coalition for a Healthy California, a leading advocacy group aiming to improve Latino health care. To reach parity today, California would need to produce an additional 27,000 Latino physicians—instantly.

There are recent signs of progress. A 2012 report from the Association of American Medical Colleges shows that, nationwide, minority applicants to medical school increased for the third straight year. Last year, applications from Latino students hit an all-time high of 1,731, a six percent increase over 2011.

However, the Latino population is growing at an even faster rate. This year, they are on track to surpass whites as the state’s largest ethnic group. The pipeline through medical schools just can’t keep pace.

Guerra believes educators must address the problem with new ways of assessing candidates and measuring success. “Telling someone they can’t become a doctor based on a grade, I think, is a disservice,” he says. “Everyone learns differently.”

The doctor’s prescription is simple: Develop talent. Don’t just select it.

On his desk, Guerra keeps a framed photograph taken of him last year with a group of pre-med students at Pomona. It was his first trip back to his alma mater, and he found students hungry for guidance. They signed the picture: “Thanks for your encouragement!!”

Guerra, however, came away discouraged. “That was just a reminder of, es la misma cosa—still the same old thing,” he says. “It was like meeting myself all over again, meeting students who were struggling to pursue their dream of becoming a physician, and maybe they had gotten a C+ and were feeling that pressure.”

Professor Roberto Garza-Lopez, a Mexican immigrant who now chairs the Chemistry Department, believes things have improved at Pomona since Guerra’s day. He cites several programs designed to help Latino students—mentoring, tutoring, peer support—that didn’t exist when he began teaching there 22 years ago. And today, the College has more people of color on the faculty to serve as role models, says Garza, who in 2007 became the first Mexican citizen to be named full professor in the sciences at Pomona.

Mentoring is key. Establishing a one-to-one personal relationship with students can make the difference between success and failure. Students in crisis, whether personal or academic, must feel they have a lifeline, says Garza, who encourages students to email or call him any time, even on weekends. They can also come to his lab at night for counseling, or just a pep talk.

“So the door is always open for them to encounter a professor who is willing to help them,” says Garza, who comes from a family of physicians in Mexico. “It’s this type of relationship with students where the trust is established, then the growth process starts.”

All these efforts try to head off the sense of isolation Dr. Guerra felt when he first arrived on campus. The High Achievement Program (HAP), for example, works with entering freshmen during the summer before they start at Pomona. They do coursework and research that gets them primed for college-level work; plus, they establish mentoring relationships that carry forward through that key first year, so they don’t fall through the cracks. In addition, they establish peer connections with students in the other Claremont Colleges through workshops sponsored by the Office of Chicano/Latino Student Affairs.

“That is very helpful because when they enter Pomona College they belong to a group,” says Garza. “So if they experience problems, they know where to go and whom to talk to, and they have this network of people who are trying to help them. Twenty years ago, we didn’t have that. Believe me, now they do not feel isolated.”

lopezmena1Professor Garza proudly points to several of his own success stories. One of them is Dr. Gerardo Lopez-Mena ’04 (pictured), the son of Mexican immigrants, born and raised in the blue-collar community of El Monte. Lopez-Mena—who uses his dual surname from his father, a custodian, and his mother, a homemaker—got a generous college scholarship and graduated with a degree in chemistry. But he couldn’t have made it without mentors, he says, including Prof. Garza who encouraged him to do research and made him co-author of a serious scientific paper published in the journal Chemical Physics Letters.

“Unfortunately, many of us go to medical school and don’t have the privilege of having had doctors at our dinner tables who make us feel that we belong,” say Lopez-Mena, who this year is completing his residency in internal medicine at The Johns Hopkins Bayview Medical Center in Baltimore. “But I’ve been blessed to have mentors throughout my life. So when there was someone telling me no, I had more people telling me yes. I had mentors who saw something in me even at times when I didn’t see it in myself.”

Guerra was 4 when his parents brought him to this country in the mid-’60s from his native El Salvador. His family settled in mid-town Los Angeles, just west of the Pico-Union neighborhood that would later explode as a dense nucleus of Central American immigration. Within two years, his maternal grandparents came to live with them.

Their arrival would change the course of his life. By the time he was 8, little Juan was recruited to accompany his abuelitos to their medical appointments, going by bus to nearby barrio clinics. His job: to serve as translator because they didn’t speak English.

That was a heavy and scary burden for a little boy. He worried about interpreting the medical information correctly. “It was nerve-racking,” he recalls. “My grandmother’s health was in my hands. What if I get it wrong?”

Communication was not the only challenge. Juan found it excruciating to have to witness the intimacy and probing of a doctor’s examination. He had to be there when his grandmother changed into her gown or when his grandfather had a rectal exam.

“Come on!” he says, with exasperation still in his voice. “How do you process that as a kid? Being in adult situations at that age was an eye-opener. It was just my reality, and the elements of justice resonated.”

Or rather, injustice. In those days, finding a Spanish-speaking doctor in the City of Angels was close to a miracle. Once, a doctor addressed his grandmother’s high blood pressure by telling the boy that “she’s got to stop eating so much Mexican food.” “But we’re not Mexican,” Juan responded. Maybe, Guerra says, the doctor should have just asked what kind of food his grandmother was eating. After all, she lived to be 95.

 One mild day in December, Guerra is sporting a guayabera at work. Though the traditional tropical shirt is casual, his demeanor is formal, like his table manners at lunch. During an interview, he occasionally answers questions like he’s taking a test. Is wearing the guayabera a conscious choice?

“Correct.” Does he wear it to send a cultural message, to connect with patients, or just because he likes the style?

“All of the above.”

Many Latinos, Guerra says, cling to superstitious myths about health. For culturally competent doctors, the goal is to dispel those cultural mitos without condescension or condemnation.

Some patients, for example, think insulin actually causes the death of diabetics, because they see people forced to take it at the end stages of the disease. Guerra was still in junior high school when his own grandfather died of the disease, plus complications from alcoholism, another public health scourge among Latinos. Sharing that family story can help form a bond with his patients.

It’s all about establishing relationships of trust.

“The role of culturally sensitive care is very dynamic,” he says. “It requires agility and cultural humility, because not every Latino is going to be the same. But I point to the importance of family and being able to distribute messages of health, of empowerment, of encouragement. How those messages are perceived depends on who the messenger is.”

Lopez-Mena shares that vision. His desire to be a doctor also goes back to his childhood. He was born prematurely and suffered severe asthma growing up, so doctors were his role models of success. But he also had doubts and detours. He took the MCAT three times with less than stellar results, leading counselors to steer him to other careers. After college, he used his chemistry degree to work for a pharmaceutical company, which he didn’t like. Then for a couple of years he was a PE teacher in elementary school, which he loved.

In the end, he realized medicine was his vocation. After a year of post-baccalaureate study, he was accepted at the Albert Einstein College of Medicine in New York. “Nowadays,” says Lopez-Mena, “the main reason I want to be a doctor, and the main reason why I love my job, is that I want to be an advocate for people who don’t have a voice and really transform the Latino community into a healthier one.”

Guerra had originally planned to be a family doctor, but he changed his mind in medical school. During his clinical rotations in Peoria, where there was an influx of migrant farmworkers, he saw women who came to the hospital to deliver their babies. And he was struck by how traumatic it was for them because they couldn’t speak English. At the time, there were no Latino doctors in the training hospital’s ob-gyn department.

“To see the look of fear and despair because they felt out of place during what should be the happiest day of their lives was really powerful to me,” he recalls. “For a young medical student to be empowered to make a difference during a woman’s labor by being able to speak the language was just amazing. When you think of how I was able to calm and soothe patients who were otherwise in a scared state of mind, alone and worried. I think it was almost as effective as a good epidural.”

It reinforced his own reason for choosing medicine. That motivation remains as solid as it was during that humiliating admissions interview. When the medical school dean asked why he chose medicine, Guerra explained passionately about his childhood experiences with his grandparents and his desire “to bridge the gap between quality health care and individuals of diverse cultural backgrounds.” The reason was rejected. The increasingly impatient dean asked him three times, waiting for the “right” answer. But the increasingly defiant Guerra gave the same response each time.

Wrong, scolded the dean finally. He should want to be a doctor for the sake of science.

“I knew deep in my heart that the reason for my becoming a doctor was not going to be the fact that I love science,” says Guerra. “It was more because I love my family, and I reflected on the challenges that they had in obtaining quality health care. I came into medicine because I wanted to leave it in a better state.”

The Tale of the Trees

The Tale of the Trees: The California story behind our beautiful-but-complicated campus canopy

oaktrees1

Trees number 2110 and 2111, perhaps Pomona’s most expansive pair of oaks, stand side by side and largely out of sight at the eastern edge of the Wash, far from the center of campus. The two have no grand names, just ID numbers etched on metal tags, and their centuries of survival are a silent success. “This is what happens when we leave trees on their own,” says Cy Carlberg, a Claremont-raised arborist, while taking a walk through campus on a crisp December day. Looking more closely at one of the giants, she notices an emerging area on the trunk revealing fresh-looking wood. “This is wonderful. See how this is expanding?” she says. “This is active growth.”

The College itself has seen plenty of active growth since its founding in 1887, and the changes in buildings, programs and people make it tempting to see our trees as stalwarts, rooting the campus to a time before its very existence. There is plenty of truth to that notion, particularly when it comes to Pomona’s coast live oaks and sycamores. And yet the history behind our trees—which also include eucalyptus from Australia, crape myrtle from China, coral trees from South Africa—is more tangled than the neatly-maintained landscape lets on. Pomona’s soaring sentinels form more than just a scenic canopy. The trees reveal a Golden State story, but one with ties to nearly every continent.

Strolling through campus, Carlberg is quick to identify noteworthy trees with roots around the globe, from “very, very old” Italian stone pines towering over Walker Beach to an unusual Chinese wingnut tree in front of Harwood. Well-groomed Pomona trees like these helped shape Carlberg’s career path. She was in her early teens when one day her father drove her past campus and she “saw a tree that I knew had been pruned just impeccably.”  Soon, she was working for the tree care company that did the work. Later, as she went on to get her degree in landscape architecture, Carlberg became fascinated with Ralph Cornell, Class of 1914 and Pomona’s first landscape architect, and today she treasures her copy of Cornell’s Conspicuous California Plants given to her by his widow, Vera. The arborist is only one of a number of Ralph Cornell aficionados still found among plant-lovers in the region.

euc1 THOUGH CORNELL GRADUATED a century ago, his plantings remain a conspicuous presence, and the late landscaping genius is still central to the story of Pomona’s intriguing mix of trees. Cornell was fascinated with foliage from his first semester at Pomona, when he took a botany course with charismatic Biology Professor Charles Fuller Baker. Soon, Cornell had a business venture selling saplings grown from Mexican avocado seeds, and the profits enabled him to go on to Harvard and earn his master’s in landscape architecture. Cornell found his way back to Southern California, and Pomona quickly hired him as the campus’ landscape architect, a role he would hold for four decades.

This all comes from a senior paper by biology major Nik Tyack ’11, who learned about Cornell while examining campus water use on a sustainability fellowship. Tyack became so taken with the work of Pomona’s first landscape architect that, along with writing the paper, he also co-founded the Ralph Cornell Society, a group of students devoted to tending native plants on campus.

Cornell’s advocacy for California flora is well-chronicled in Tyack’s paper, which recounts the landscaper’s pioneering ponderings about the state’s plants and the possibilities of creating a “Genuine Southern California Park.” But once he became Pomona’s landscape architect, Cornell took a very different approach, “designing mind-boggling creations in which plants from areas as far apart as New Zealand, Central Asia, Europe, Australia, Japan, China, South Africa and Southern California mingled in a single landscape,” writes Tyack, now an environmental consultant back East.

Why the shift? Simply put, Cornell cared most about the look and design of his landscaping and, according to Tyack, bringing in plants from around the world was “merely a means to create beauty.”

This was the thinking of the time. With a climate unique for North America, the state became a center for arboreal experimentation. “People began to think of California as this place where you had this cosmopolitan mix of trees from around the world,” says Jared Farmer, author of Trees in Paradise: A California History. That thinking was fed by the acclimatization movement, which sought to systematically and scientifically spread species globally to increase local biodiversity. “The idea,” Farmer says, “was to find the perfect place” for a particular plant.

The reality of this experiment wasn’t so perfect, with the state’s long-ago eucalyptus craze serving as a case in point. The Australian imports were widely touted as super-trees, Farmer says, growing to great heights in California during their late 1800s heyday, when they were planted along College Avenue at the western edge of campus and in countless other locales across the state. In time, though, these trees brought worries ranging from fire risk to falling limbs, leading to their removal in some locales. (In his book, Farmer notes the tragic 1998 incident in which a falling eucalyptus branch killed two Pomona students on their way to class.)

Eventually, the focus at Pomona and beyond began to shift back to native plants. Cornell was on board, returning to his advocacy for native plants later in life. In a 1966 letter urging preservation of the Wash, Cornell sang the praises of its oaks and sycamores. “They are part of the heritage which we should protect and, yet, in much of California, they are being decimated and destroyed by the march of ‘progress’ in a manner most frightening to behold.”

CORNELL WOULD BE REASSURED by the direction Pomona is marching in today. When it comes to campus trees, the emphasis now is on native ones, though not exclusively. And grounds crews keep planting new ones as the College works to preserve—and in some cases expand— green space. As an example, Assistant Director of Grounds Kevin Quanstrom points to a previously- paved area north of Big Bridges recently converted to open space, with walkways and seating. Add to that a perfect row of California fan palms, the only palm native to the state, along with newly-planted sycamores and, of course, oaks, which make up about a quarter of Pomona’s roughly 4,000 trees, reaching into every corner of campus.

These native oaks are “the classic tree of Mediterranean-climate California,” notes Bart O’Brien, co-author of California Native Plants for the Garden. Not only are the oaks sophisticated ecosystems unto themselves, he points out, but their acorns also once played a role in the seasonal food supply for Native Californians. Today at Pomona, the old oaks help tie the campus to a time long before the College was established.

Deep in the Wash, where the wild oaks reign, trees Nos. 2110 and 2111 hold their ground and keep a secret. Arborist Cy Carlberg has a hunch that these two are somewhere in the range of 300 to 400 years old. “It’s just a gut thing,” she says. “I look at old wounds. I look at the way the wood has adapted. It’s just a feeling.” The trees’ size alone doesn’t prove their agesthe rate of growth can vary greatly with water supply. Without intrusive measures, there’s no way to count the rings and know for certain their ages until these oaks come down through rot or storm. And that day, we can only hope, is still centuries away, leaving a lingering mystery to this California tale.

 

The Heart of the City

herman1

Nestled between the skyscrapers of downtown L.A.’s financial district, the Los Angeles Central Library can be hard to spot at first glance. Just on the other side of 5th Street is the U.S. Bank Tower, the tallest building on the West Coast. Yet Robert Herman ’51 instantly zeroes in on the library entrance, pointing out something that sets it apart from other seemingly deserted downtown attractions on this chilly December morning: “Look at all these people coming in and out. This place is lively; it’s somewhere people actually go!”

 An emeritus professor of sociology at Pomona who focused on urban issues for much of his career, Herman is a long-time advocate for the renewal of L.A.’s downtown. He sees the library as a model for a successful public space, serving as both a local landmark and a vibrant hub of activity in the heart of the city.

 Herman’s affection for the library grew out of his long-running exploration of the central city by foot. The author of Downtown Los Angeles: A Walking Guide, Herman has given hundreds of walking tours around the city’s hills, plazas and parks.

 As he dug into the history of old L.A. haunts while working on his book, Herman found himself making frequent trips to the library to use its archives and records for research. His appreciation for the place stems from being both a pedestrian and an investigator. Plus, there’s the aesthetic appeal: “Architecturally, I think this is one of the best buildings in the city,” says Herman.

 The 1926 Art Deco structure was designed by architect Bertram Goodhue and sculptor Lee Lawrie, a renowned duo who crafted other famous sites such as the buildings in San Diego’s Balboa Park. With a blend of Egyptian and Mediterranean revival styles, the library evokes the image of a classical temple or academy, infused with an early 20th-century attitude of modern progress and purpose.

 As an example, Herman points to the pyramid that crowns the library’s uppermost floor. Rising from a base of columns, the pyramid is covered in tiles forming an elaborate mosaic of a sunburst and topped by a sculpted torch.

Herman says the images represent the light of learning and knowledge, expressing the lofty sentiments of its designers.

 Inside, Herman leads the way to the central rotunda, the focal point of the historic building. Wrapping around all four walls is a richly colored mural by famed American illustrator Dean Cornwell, depicting a series of eras in the history of California and the founding of Los Angeles.

 On the opposite side of the building is the expansive Tom Bradley Wing, added after a fire in 1986 caused widespread damage. The wing is anchored by an immense glass atrium that extends several stories below ground. As Herman points out, the large windows and glass roofing allow natural light to filter through every level, making the space more inviting.

 “Even though it’s underground, it doesn’t feel like you’re in a cave. It’s open and bright down here.”

 For Herman, however, the beauty of the building comes second to the service it offers the community. “Anyone can feel comfortable using this place. This is the one spot in all of downtown L.A. that has something to offer to people from all backgrounds.”

 He recalls coming downtown in 1989 for the building’s reopening after a series of arson fires and a massive renovation. Lines formed around the block as people crowded to get their new library cards. Parents brought their kids to show them where they had done their homework and checked out their first books as schoolchildren.

 “It meant a lot to me to see people sharing these memories with their families, showing their appreciation for the place,” says Herman. “As long as I see people showing up here, it tells me that this is a place that the city still needs.”

The Dark Side

donner

Set on a clear alpine lake, surrounded by the peaks and forests of the High Sierras, Donner Memorial State Park could be nothing more than a pleasant, scenic getaway, if it weren’t for that infamous name. Just west of the town of Truckee, the park marks the site of one of the grisliest and best-known pioneer sagas of the American West. In the fall of 1846 the Donner Party, a group of would-be immigrants to California from the Midwest, found itself snowbound in the Sierra Nevada. As supplies ran out, desperation kicked in, and those who hadn’t already perished began to cannibalize the bodies of the dead. Less than half would survive.

 At the park, history buffs can explore a museum that details the Donner ordeal and its place within the larger story of California’s settlement. A sculpted monument recognizes the pioneers who made the arduous trek, standing near the spot where families took shelter in wooden cabins. The park will get a facelift with the completion of the High Sierra Crossing Museum, slated to open this coming fall. The new center will take an updated look at the tangled legacy of pioneer expansion in the region, considering its effects on local environments and Native American communities. The park’s stunning location also makes it an ideal place to spend time outdoors. There are campsites on the shores of Donner Lake, and a light hiking trail that winds around the water. The resorts and nature areas of Lake Tahoe are also a close drive away.

 History Professor Victor Silverman, who touched on the Donner story in his book California: On-the-Road Histories, says the site’s appeal may be the powerful contrasts between landscape and history. “To be in a place like Donner Park, which is spectacularly beautiful, and to also think about the tragedy that lies hidden in the past there, is really compelling,” he says. Silverman, whose work considers the political and cultural forces that have shaped California’s society, thinks the tale of the Donner Party reveals some of the complications that inform our perceptions of the Golden State. “The California myth has always had a light side and a dark side,” he says. “These people came here to make their families prosperous, taking this adventurous journey to the west, but it turned into a horrible disaster.”

A Church With a Memory

sandoval1

Professor Tomás Summers Sandoval Jr. peeked through the front doors of Nuestra Señora de Guadalupe, a gleaming white church on a steep street at the edge of San Francisco’s Chinatown. Inside, a red light glowed over a patch of black-and-white tile, and a musty odor wafted out, the scent of decades of rites and rituals, of fading memories.

 Summers Sandoval wrote extensively about the church—a vital religious, educational, political, and social center for Spanish- speaking Catholics—in his new book, Latinos at the Golden Gate, which explores the rise of the city’s Latino community.

 The archdiocese never once let him inside, the professor notes, but the lack of access didn’t impede his research into the last remnant of a once lively Latino neighborhood. “Most of the time when you’re writing about history, the people are no longer there, the community is no longer there,” says Summers Sandoval, standing outside Guadalupe Church. “That’s history.”

 In his book, he traces the roots from the days of the Gold Rush when migrants first arrived in search of fortune. By 1871, Latin American diplomats and business elites started raising money to build a Spanish-language Catholic church to unify a diverse population, hailing from countries that had strong rivalries. “We who belong to the Spanish in this city, will never achieve strength or respectability while we do not also have unity,” they wrote in a fundraising circular.

 Founded in 1875 and rebuilt in 1912 after the city’s great quake and fire at a cost of $85,000, the Moorish Gothic style church could hold 700.

 The neighborhood around the church (bounded by Columbus Avenue, Filbert, Washington and Jones streets) grew into the Latin Quarter, a residential and commercial district catering to Spanish speakers. The church fostered solidarity, holding a unified Mass commemorating the independence days of Mexico and Chile each September. Parishioners also carried on traditions, continuing the same rituals, prayers and songs on feast days of their homelands.

 By 1950, though, Guadalupe Church began to decline. The Latino population—which more than doubled between 1945 and 1970—moved to more affordable neighborhoods such as the Mission District. The construction of the nearby Broadway Tunnel displaced some residents and reduced attendance, and Chinatown encroached, transforming the blocks around the church. Yet even when Latino families moved out of the neighborhood or into the suburbs, many maintained strong ties, returning to Guadalupe Church for baptisms, confirmations, first communions and first confessions.

 Declining membership brought the closure of Guadalupe Church in 1991, and the building eventually housed St. Mary’s School for 15 years. The space is now vacant, and efforts by the Archdiocese to sell the historical landmark met resistance from activists who want to preserve the church for use by the Latino community.

 From the front steps, there’s a view of the Bay Bridge and the tip of the Transamerica Pyramid, and the street below hums with the sound of cable cars rolling past. The bells are gone from the church’s twin towers, but a stunning mosaic of the patron saint remains on the façade above the front doors, in a red gown and blue mantle adorned with stars, streaming rays of sunshine—the same saint that generations of San Francisco Latinos venerated here.

 The church, says Summers Sandoval, remains a reminder of the people’s struggles, “the result of the success of early century immigrants to create a home for themselves in the city, a place they could claim as their own.”

Digital History

 Pomona Alumnus Ashlee Vance

How to tell the story of Silicon Valley—land of entrepreneurial visionaries, booms and busts, and the quest for machines to extend the farthest reaches of the human mind? For Ashlee Vance ’00, a writer covering tech for more than a decade, a good place to start is across the street from his house in Mountain View, Calif., at the Computer History Museum. The building is part of the story; here once were headquarters for SGI, maker of hardware and graphics innovations that enabled work on the first Star Wars films and provided sought-after speed for Wall Street trading.

 “Computing moves so fast that people don’t take time to stop and document it,” says Vance, author of Geek Silicon Valley and writer for Bloomberg BusinessWeek. Striving for the new new thing means that there’s a tendency to chew through the old stuff and spit it out. But the museum offers a kaleidoscope history of technology (2,000-plus years and counting) and shows how the ways we work and play have been rewritten by computing, with design aesthetics that range from a wooden abacus to steampunk to the Jetsons. There’s the big hardware from the pre-digital (and even pre-vacuum tube) age, starting with Charles Babbage’s “Difference Engine No. 2,” a massive contraption filled with metal gears designed in the 1830s. (It was only built last decade, to see if it would actually work. It does.) Another hefty device, Herman Hollerith’s desk-sized “Electric Tabulating System,” used punched cards to compile data for the 1890 U.S. Census.

Think colossal for IBM’s SAGE system, built in the 1950s (at the cost of $94 billion in today’s dollars) to provide warning against a Soviet nuclear attack. It required hundreds of operators—some who spent mind-numbing hours staring at a screen, watching, waiting. Thankfully, there was a built-in ashtray.

 Think cool (including Freon) for the Cray-1, both the fastest computer on the planet after it was finished in 1976, with 60 miles of hand-threaded wire inside, and “the world’s most expensive loveseat,” thanks to a leather bench wrapping around the outside. “It has so much more character than computers today,” Vance says.

 It’s the story threads that make the museum displays especially compelling, Vance says. Early work on enormous scale wouldn’t have been done without massive government funding. But standing on the shoulders of those literal giants are the smaller machines which, together with a DIY attitude and a late-’60s desire to expand the possibilities of human experience, led to the first virtual reality goggles (1969) and, through the Homebrew Computer Club, the Apple I.

 Don’t miss the game room. Start with the first Pong machine—a curiosity when it was installed in a bar, “but this kicked off the videogame revolution.” That made Atari into the fastest-growing company ever. They’re not any more. But “people tend to underestimate video games,” Vance says. “They push limits of software, of graphics, of silicon.”

 The seemingly limitless realm of the Cloud is a place we know well enough now—though where is it? Here’s an early server rack, the machine sagging in the middle, that belonged to a fledgling Google. “They had to use cheap hardware, and the software had to make up for when a disk drive or chip would fail.”

 What would Vance imagine for the next wing of the museum? The interplay of hardware and software in what we drive—or drives itself, especially under electric power; and the coming revolution in robotics. Plus, he says, “Down the road is a company working on a flying car.”