flwyd: (big animated moon cycle)
16 years ago on November 30th I titled a post Persimmons, Not Parsimony because I'd been tickled orange to find a bowl of persimmons in Charlie's Café, the largest eatery on Google's Mountain View campus. It was the first day of Noogler Orientation and an inflection point in my life. 24 years later I attended an improvised Dickens performance at San Francisco's BATS Theater at which the audience answer to "What reminds you of the holiday season" was "persimmons!" and it sent the story off to a sweet yet tannin-infused evening of long-form improv comedy.

To round the night out, across the street I spotted The Interval, part cocktail bar/artisan café, part museum for The Long Now, an organization devoted to thinking 10,000 years in the past and 10,000 years in the future. I recall hearing vaguely about this group around 2009, and it's fitting that I landed in their bar after sixteen rotations of Earth's celestial gears: on display was a model of a component to compute the equation of time in their 10,000 year clock. Some of the code I wrote in my final months at Google computed the sun's elevation above the horizon at a given instant…in SQL. Over the last several years I've toyed with the idea of writing a book about the various ways humans keep track of time, but I'd forgotten about the Long Now folks… perhaps they could be a human element that weaves a narrative into my nonfiction tome.

There's an alternate history to my professional and personal life. In the fall of 2009 I had no long-term commitments. I had assumed that Google's hiring process involved choosing a location after passing the interview, not realizing that my acquaintance had referred me to a specific Google Boulder position. After quitting my job in early 2009 and traveling for the summer I had imagined that I might end up in the Bay Area, the center of gravity for the computer programming world and a place that hadn't yet lost the luster of early 21st Century techno-utopianism. San Francisco seemed like the hip place to be when I was 30, and I was curious if I would choose to live in biking distance of an office in Silicon Valley and commute to The City By The Bay for cultural enrichment, or whether I'd try a life in the dense urban space and make US-101 my daily journey. (I also interviewed with a company in DUMBO, Brooklyn, near the hipster haven of the other coast, Williamsburg). I wasn't upset to stay in Boulder ("You're already from there," Molly quipped), and as I watched Googlers complain about everything in the Bay Area from traffic to housing to taxes to rain ("You live in a place affected by drought and you're complaining about the rain" I memeed) I got to feel pretty good about sticking to my mile-high xeric roots. I continue to chuckle whenever someone moves to Boulder and is wowed about how cheap the housing is and how efficiently traffic flows.

Geography is destiny; where we are determines so much of the course of our lives. Had I moved to California I wouldn't have connected with Kelly in 2010, we wouldn't have lived through the 2013 flood, we wouldn't have gotten married on Talk Like A Pirate Day, we wouldn't have bought a house, we wouldn't have our cats. I'm in the Bay Area again this week because we visited Kelly's sister and our nephew, neither of whom I would've recognized as anyone special in this alternate history. I would have met other people in San Francisco and around this saucer of mountains. I would have partied with Burners more than once or twice a year. I would have picked up different hobbies, fallen in love with different people, built community in different places. Who knows if I would've stayed at Google for a decade and a half—over the last 10 years Facebook and Amazon kept trying to recruit me to Seattle for some reason, but I imagine a Bay Area software engineer gets lots more unsolicited job inquiries, ones that don't involve a change in homes too. At Google Boulder I made friends with the sourcing team, the folks who identify those potential candidates who aren't looking for a job. Engineering and People Ops had lunch on the porch together, went to the same office parties, and a pair even got married. That cross-organizational connection doesn't happen as much in Mountain View: there are far too many Bay Area Googlers to put unrelated jobs together in the same building. All things considered, I'm happy with the happenstance that kept me at 40 degrees north, 105 and a quarter degrees east, rather than sending me on a long-term assignment to 37 and a half degrees north and 122 degrees east. The weather here is pleasant year round, but that's not a great way to keep time.
flwyd: (red succulent)
My favorite Google perk so far? There were two baskets of fresh persimmons in the cafeteria for lunch. Not only are you never more than 150 feet away from free food, it's succulent tasty free food.

Okay, so fresh persimmons might be more of a California perk than a specifically Google perk. I saw a guy yesterday with two persimmons in a bag, so I'd planned to go on a persimmon hunt anyway. But the copious free food illustrates Google's understanding of software engineers. Eating is part of programming.

Eating is also how humans bond.[1] So by having cafeterias and micro-kitchens all over campus, Google can foster natural communication in a community of significant size. At my previous job, I remember a lot of important decisions and designs that happened in the kitchen rather than in a meeting room.

Google firmly believes in open access within the organization -- by default, all documents employees create are visible to anyone else in the company. But with great knowledge comes great responsibility, and they rely on employees not to share that information with the outside world. So while I'd love to tell you how many people make it all the way from application to offer and the impressive size of Google's aggregate storage, those are things that competitors would love to know, so they'll have to remain private.[3] There's a strong history of public blogs talking about experiences at Google, so I'll still be able to share my perspectives and insights on things at a high level, and Google relies on word of mouth to get their message out. It's just that I need to make sure my "That's awesome!" response passes through a "Who can I share the awe with?" filter. I didn't have a problem with this at my last job, but information about Google is a lot more exciting than information about government record keeping.


[1] I think Steven Pinker's How The Mind Works quotes Dear Abby (or Emily Post?) about dating. It goes something like "A date should feature entertainment, food, and company. As time goes on, more and more company can replace entertainment, but food must always be present." I'd like to find the original quote, but my copy of HTMW is in storage and my several web searches had no luck.[2] Anybody have a proper cite? Update: Thanks to [livejournal.com profile] dr_tectonic for citing Miss Manners:
There are three possible parts to a date, of which at least two must be offered: entertainment, food, and affection. It is customary to begin a series of dates with a great deal of entertainment, a moderate amount of food, and the merest suggestion of affection. As the amount of affection increases, the entertainment can be reduced proportionately. When the affection IS the entertainment, we no longer call it dating. Under no circumstances can the food be omitted.


[2] The irony of failing in my first web search task after joining Google is not lost on me.

[3] There's probably also some degree of law and sausages at play. It's easy to abstractly be in favor of open communication, but sometimes you're better off not knowing.
December 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 2025

Most Popular Tags

Expand Cut Tags

No cut tags

Subscribe

RSS Atom
Page generated Saturday, January 3rd, 2026 08:37 am
Powered by Dreamwidth Studios