I was hit by an SF TechBus and I still bike to work. Here’s why.
Two years ago I was hit by a San Francisco tech commuter bus biking home from work near the Caltrain station. I was rushed in an ambulance to the hospital and released with minor injuries. I live with some amount of pain in my body every day since then. (If you look closely, you might be able to see that I still walk with a bit of a limp sometimes.)
So why do I still bike to work?
Well first, there are the obvious reasons: exercise, frugality, a dislike of traffic. (It’s also just faster than other modes of transport at the times I’m typically traveling.) Then there are the almost obvious but deeper reasons: biking aligns with my values, including my desire to be good to our planet, and my belief in the value of a healthy body and mind.
Underneath all of that, though, I discovered more interesting reasons...
I work in innovation and design consulting. Companies come to us to help them invent and realize new products and businesses.
Recently, a need to take some days off from biking to work gave me a chance to notice how biking to work totally primes my mind for the kind of moment-to-moment assessment of opportunities, risks, everyday victories, and trade-offs which are at the core of my design work. This break gave me a chance to observe how biking activates me mentally and physically. Navigating the SF streets in rush hour on a bike brings me into full aliveness -- to avert the possibility of immediate dead-ness. Something about being not that far from the edge, even from death, is very enlivening! By the time I arrive at the office, my mind is already fully engaged in the dance of life. Almost better than coffee.
Can I squeeze between the two potholes and the train tracks?
Is there room for that car door to open?
Is she changing lanes or not?
What is the risk of there not being any parking available?
Do I need to mitigate that?
What do I want to do after work, and what’s the risk of getting blocked in?
Every ride through the streets of SF is a spontaneous improvisational journey requiring high alertness and sensitivity, and in that way it’s a tiny fractal piece that is somehow representative of my entire life. I get to, need to, feel fully alive.
I noticed that I really missed biking to work on a number of levels. Each journey on the bike is also a design opportunity. What do I want to design for today? Speed? The scenic route? A bit of both? Add an extra stop, or get there early?
Hearing all of this, you might ask: have I learned anything from being hit by a tech bus?
It turns out I’ve learned a lot.
I’ve learned that there are things that are a higher priority than going faster. I’ve learned that there are times when being faster really matters, when it’s all on the line. I’ve been reminded that there are things (people, tools, and equipment) that are worth investing in, to enable things to proceed safely and efficiently. And in dealing with bike crash repairs, I’ve been reminded that constantly knowing where I can add the most value versus when to outsource is the way that I maximize awesomeness with finite resources, obtain the best outcomes, and feel the most fulfilled.
It’s interesting how there are so many parallels between my biking life and my working life.
So after all of this, why do I still bike to work?
Because despite it being risky and sometimes demanding, feeling fully alive is worth it.
In this second chapter of the IoT series, we’ll show that IoT is about the “Information of Things.” The value of IoT follows the Pyramid of Knowledge, generating increasing value as data gathered from IoT devices is processed into information and the resulting knowledge & insights.
If you’re not impressed with the innovations the agri and foodtech industries are continuing to generate, then you’re not paying enough attention. Here are the two major considerations shaping the future of this perennially hot mega-tech market.
Over the last six years, we’ve made an effort to build diversity, equity, and inclusion into the fabric of our organization. From the beginning, we’ve taken an iterative approach, revisiting our initiatives, processes, and policies to make improvements over time, multiple times. Now that we’ve made significant progress, we want to share insights that we hope will help you make positive change at your own organization.
Puget Sound has its share of challenges—homelessness, traffic congestion, and affordable housing to name a few. But, an underlying issue is that we're not working together to find solutions. I'm active with the Washington Technology Industry Association's Ion program—a collaboration incubator that brings together tech, government, and not-for-profits to tackle community challenges. In this video report, I explore this important topic.
GitLab was recently in the house for DevOps Stories Seattle, "a single day symposium dedicated to real-life DevOps transformation stories." Hosting the event here in our Seattle office was a great opportunity for us to cross-pollinate with other people and organizations that are using GitLab to solve their own challenges. Software Engineering Program Lead, Jason Haensly, joined in on the knowledge-sharing with a presentation describing how we use GitLab throughout the product development process, and why we think it's such a win.
Synapse is a product development firm. We work with the best companies in the world to drive innovation and introduce cutting-edge devices that positively impact our lives. Fueled by a desire to solve complex engineering challenges, we develop products that transform brands and accelerate advances in technology.