December 31, 2015
four times i said yes in 2015 and one i didn't
Snow, sky, and frozen lake are painted the same color, pine boughs laden with white, icicles hanging from the eaves reaching towards the busy bird feeder outside the cabin window. The larger pine grosbeaks are moving in on the black-capped chickadees, a silent drama playing out in ruffled feathers and dropped seeds. Aggrieved, the chickadees perch sideways on the icicles.
At this point, you’re wondering when I started paying attention to birds. Well, Occam’s razor tells all: this dogeared copy “Birds of Minnesota Field Guide” has forgotten more about birds than I’ll ever know. And Gabe looked those up while I tried to take pictures of birds through glass and pondered the shadowless expanse that is the Boundary Waters on a cloudy winter day.
My 2015 is ending as it began, in the far reaches of northern Minnesota’s lake country near the Canadian border. The cell towers haven’t reached this far, but this cabin has internet (unlike last year’s rental). Snowshoeing, playing board games, and eating Christmas cookies in front of the fire leaves plenty of time for contemplation.
The quiet of these few days casts my hectic 2015 into sharp relief. This year I spoke at a company’s internal devops event, eight meetups, and eleven conferences in three countries (not counting two other conferences where I gave a vendor talk). By miles flown, I circumnavigated the globe more than three times. I joined the devopsdays core organizer team and put on the second devopsdays Minneapolis with our great local crew. I joined the Velocity program committee and read so very many talk proposals that I think I could now write (and possibly have written) them in my sleep. I changed jobs from one I loved to another that’s the definition of exciting new challenge.
It’s been a stellar year, and I’ve tried to identify why: I think it’s because I defaulted to yes.
One
While I gave about six different tech talks in 2014, 2015 had just two main themes (platforms and distributed teams). Giving a version of my “Docker in production” talk in mid-January meant I became comfortable with speaking on this material earlier than I’d thought; I gave it half a dozen times before OSCON.
After presenting at OSCON to an overflowing room (since apparently fire codes meant only about 500 people could enjoy it), I walked into the speakers lounge the next morning intent on breakfast. What I encountered before I could make it to the coffee was the O’Reilly speaker manager Audra saying “hey” in that unmistakeable “there’s a request coming at the end of this greeting” sort of way. They’d had a speaker with a crisis; could I speak again? Of course I said yes. (I asked the second packed room if any of them had attended the previous day’s version, and to the one raised hand, I said, “I’m not telling all new jokes just for you.” People thought that was funny, but it was just honest. I’m liable to repeat myself. It’s probably fine.)
As an organizer of smaller-than-OSCON events, I empathize with the turmoil that the unexpected brings. (“Fuck it! We’ll do it live!”) I’m glad I felt comfortable enough to step in (and it was exciting when the conference chairs mentioned my repeat engagement in that morning’s opener). Someday I should watch both videos and see how similar they are. I did manage to stick the landing for the second one at exactly 40 minutes without a clock or room host. (I know leaving time for questions is optimal, but I do tend to run long. Like that meetup in Chicago when I took questions throughout and talked for over 90 minutes until the organizers said I was going to make people miss the last train…)
Two
Like I’ve been telling the Bay Area recruiters for years, snow is a feature, not a bug. If I were interested in moving to San Francisco, I’d have done so during the first tech bubble. I like my northern home state with our 11,842 lakes (even if they aren’t entirely frozen yet this year - “I wouldn’t go out on the lake”, said the cabin owners, though the deer appear to be ignoring that recommendation). As much as I value face time with my team (and I do!), I love being able to decouple where my employer is located from where I live. So when I switched from DramaFever to Pivotal, I went from an east-coast org to a west-coast one… but, happily, didn’t need to move.
After being on call for production infrastructure from 1999 to 2015, I traded in pager duty for more travel as a tech advocate for Cloud Foundry, a pretty sweet open source project. (See your US, UK, or Australian government innovation offices for more details.) I felt somewhat conflicted about walking away from full-time ops, even after I told Andrew yes. Do I no longer look like an engineer? Am I opting out of being technical? Nope: still technical, but no more split focus. When I was working in ops, I was writing talks in my spare time and fitting conferences around work; now I focus on community and communication while still learning about tech, and relax more even though I travel lots. Ask Tim who moved on from ops to do product for Joyent; you eventually stop reaching for your phone wondering if you’re oncall and left it on silent. :)
This change was a significant decision, but four months in I am so very glad I took the chance on something entirely new. (Helped that I went to go work on an amazing team full of people who challenge me and encourage me to learn!) And working for a vendor for the first time means I’m learning more about the business of software than I understood before, while advocating for open source means I’m happy to share ideas with everyone in the community.
Three
I had a lot of travel lined up for 2015 even before I joined Pivotal at the end of August. (One of my first meetings with my new boss was going through a google spreadsheet entitled “Bridget’s Kinetic & Potential Commitments”. Spoiler alert: most of the potential converted into kinetic, and I was home about 15 days between Labor Day and Thanksgiving.) So when the opportunity to speak at RICON came along, I was inclined to say no. The timing was such that I would still be jet lagged from almost two weeks in Europe for Velocity EU in Amsterdam and Cloud Foundry Summit in Berlin.
On the other hand, I wanted Caroline to be happy, and it was a conference I’d never before attended. I brought the same talk comparing distributed systems and teams that I’d given at Operability in London, but since I was awake at 4am (the joys of going from UTC+1 to UTC-8), I revised it day-of. The talk ended up better for it, and I met new people there!
Conference protip: the people you meet or reconnect with at any conference are the best part. Even more than all the fun livetweeting or presenting or track hosting or whatever else you might get up to. And if you’re going to speak, the most fun per minute is in co-presenting (especially if you’re lucky enough to work with Peter or Casey).
Oh, and my attempt to go home for a day between Berlin and San Francisco was foiled by KLM delays causing Joe and me to miss our US-bound flight at Schiphol. He still won’t let me hear the end of me “abandoning” him in Amsterdam and flying (via Detroit) right to San Francisco.
Connecting flights, like csh programming, considered harmful. I wish everywhere had direct flights to everywhere else, or better yet, I wish we had teleportation. Although then teleportation would be lossy and we’d all be complaining about how we’d left our hearts in San Francisco, where Karl chills the air.
Four
I’ll be the first to admit I’m the uninvolved sort of alum. I live a short bike ride from my alma mater and work in the field of my degree, but I never go talk to Today’s Youth. Mostly it’s that I’m busy with a side of maybe-not-a-role-model, but when a former co-worker asked me to meet with a seventeen year old girl he coaches in sportsball, I realized the truth: I am conflicted about giving The Youth an unvarnished look at reality. Tech isn’t the most welcoming place for, well, anyone. I know how lucky I am, and yet I still feel like I’ll never be most people’s Platonic ideal of a techie. I figured that talking with her would be a disaster and end in tears (probably mine).
And you know what? I was totally wrong. I mean sure, she’d never heard of abstraction and had only the vaguest notion of what “the cloud” might be. (Obviously I told her about the cloud-to-butt plugin, because I am a Responsible Adult.) But she knew perfectly well that the industry and the internet are full of not-so-great actors, and that didn’t worry her one iota. What she wanted to know was what it’s like working in software. The popular perceptions steered her towards a picture of a lone (probably male) basement-dweller and I was happy to tell her that’s nothing like my reality. (Even though I’m on a distributed team and work alone sometimes, I don’t have a basement. Which makes tornado season interesting.) She was excited to hear that software is a team sport with collaboration and sharing! Go go gadget devops!
So maybe in 2016 I’ll make time to show up at the U’s Computer Science department and talk to the undergrads. At the very least, I could tell them to take a few psych and business classes. Like Astrid says, software is made of feelings. I hear rumors of no distributed version control being taught in school (wat) but really I’m more focused on the part where we might want to practice negotiation and clear communication and compromise and sharing. You know, just like real life.
Five
You’re waiting for the no. And sure, I had to say no (see also: never moving to SF - sorry!), but this is a shiny happy end-of-year post, so let’s go with a technicality.
One last yes that made a big difference for my 2015… I said in 2014. :)
I joined Arrested DevOps as a co-host in November 2014. Matt and Trevor already had recorded a year of great shows, and I knew going in that I’d be able to chat with fascinating people and learn lots. What I didn’t realize is that at nearly every conference and event throughout the year, in whichever country I found myself, I would run into fans of the podcast!
Thank you all for listening; I’m glad we can share your commutes or flights and bring interesting conversations into your days. Thanks to all our guests and my co-hosts for making my first year of podcasting so rewarding. If you haven’t been on the show yet (or have!) but want to be, let us know! Looking forward to many awesome new episodes.
Whether or not I mentioned you by name, if you’re reading this, you’ve probably made my 2015 better, and I’m grateful. Thank you.
I’m excited for 2016. Definitely will be visiting Toronto and Bangalore and Austin, and probably many more cities. Maybe I’ll visit you! Want me to show up and talk about devops, cloud, platforms, distributed teams, containers, or some combination thereof? Let me know, because I’ve got to level up in Flying: The Game if I want to ever rate those nifty lie-flat beds. Plus, I love sharing ideas and hearing about what’s working for you.
May your 2016 be full of saying yes to exciting possibilities! And hopefully more sunflower seeds than this bird feeder, which could lead to some dangerously underpopulated bird territories of the northern taiga if we don’t refill it. I’ll look into that tomorrow; it’s a whole new year.