Sky
1:49 am and it’s time I started writing again before getting sucked into a long twisty tunnel of code. I’m on leave from Google for a week or so after the birth of my second son and now is as good a time as any to take stock and reflect on what’s going on.
The photograph above is taken near the summit of Windy Hill, a hike I used to do fairly often. This is the first time I actually made it to the top on my bike, and it was a lot harder than it should have been, but then I’m getting up there in years, finally.
The view near the top is just spectacular. The coastal fog blows over the mountain top and breaks up into these incredible wispy clouds, and they just seem to move so fast. It’s as if you have the sense of flying even when your feet are on the ground.
I actually had my doubts about making it to the top this time. Even though the ride isn’t technically, there are some steep sandy sections and my balance is a little off. Last time I attempted it with a friend I had to bow out half way up because I was feeling dizzy and disoriented. Looking down from the top of the hill I could make out a couple buildings near my home though they seemed impossibly far away. There were several points on the ride where I asked myself if I should turn around, but I just decided to take it slow knowing I would get there eventually.
Which brings me back to the pile of code that I’m tunneling through right now. I’ve spent bits and pieces of the last year working on a project that has had a lot of stops and starts. I’ve had to take it on faith that it’s important even though no one has really bothered to explain the benefits of it to me. Now we are in the final stretch, just reviewing a couple things that should be details really, only to find that some of the basic assumptions underlying the project might be incorrect, possibly momentarily, but also possibly permanently.
This realization has been creeping up on me for the last couple of weeks, and while a few weeks of misdirection is not a big deal in the scheme of things, it does make me question why I haven’t been asking the big questions about these projects to begin with. I think I need to be a lot harder nosed about these things soon, but in order to do that I also need some support. And in order to get that support I need to deliver results. But before I can really get going on things that I think will make a difference I need to finish tunneling through this pile of code and declare victory. It’s a lot of work and it takes years to learn how to read the tea leaves.
It seems to me that this one little situation is a metaphor for many of the larger challenges we’re facing now as a generation. The economic uncertainties, environmental decay, the misalignment of moral priorities, the far-to-large number of lost and lonely people in this world.
All of these problems seem huge and sometimes insurmountable. But all the basic pieces are in place - ingredients scattered around some global kitchen waiting to be sifted and arranged into some kind of cake.
So when I think about tunneling through code, even though I’m annoyed at slowdowns and misunderstandings, I’m very optimistic about the overall future. We just need to get the bike pointed in the right direction and keep pushing until we get the damn thing to the top of the hill.
Our understanding of things is so tantalizingly limited now - I can only wonder what the view will be like in five years.











