I have worked from home full-time for the past three years. I know a few people who have done so for a lot longer (decades), but, regardless of how long anyone I know has worked from home, we seem to have many of the same observations.
Thanks to the coronavirus, we are becoming a lot more familiar with the concept of “social distancing” and work from home may become more prevalent for a while. When I worked in a cubicle, I romanticized the idea of work from home. Now that I’ve done it for a while, I realize it is a unique work experience with its own benefits and drawbacks. Rather than enumerate those in detail, I’ll address some practices that I have adopted and evolved during my time at home.
I am currently reading the book “Fierce Conversations” by Susan Scott. I am on hiatus from teaching my leadership course this year, so I am taking the opportunity to refresh my content and my perspectives. The basis of the book is fairly simple:
Our work, our relationships, and our lives succeed or fail one conversation at a time. While no single conversation is guaranteed to transform a company, a relationship, or a life, any single conversation can.
This has gotten me thinking in general about conversations that have impacted me throughout my career, whether with colleagues, direct reports, supervisors, customers, or mentors.
Recently, I had an interaction on Twitter that got me thinking about a long-ago conversation in a different context that, although I had never thought much about it, had an effect on how I view the role of technology in solving problems. That Twitter interaction is here:
Koop is a really nice piece of tech. Incredibly useful. It was used to lateral @fulcrumapp data shares into situational awareness tools during Harvey response. I can’t recommend it highly enough.
It’s been a few weeks since I hit my latest milestone, but life was fairly full in the immediate aftermath. On the plus side, the extra time was good for reflection.
The milestone to which I am referring is that, on October 27, 2019, I ran the Marine Corps Marathon in Washington, DC. The race itself and the training leading up to it were the hardest physical things I have ever done. The weather during the actual race was crazy, with torrential rains for my first 14 miles or so. My finish time was a lot slower than I’d hoped, but I don’t care because I finished. I learned a lot and am already looking to do another.
Looking back on the process of training for the race, it was very much a clarifying experience. As the daily and weekly mileage ramped up, my time management skills were put to the test. It was no longer possible for me to squeeze in the mid-week training runs during a lunch hour, so it required more communication with my co-workers. To a one, they were supportive.
On the other end of the day, I needed to make sure things didn’t extend in a way that impinged on time with my family. Our kids are older and fully self-sufficient, so a lot of the logistics that were needed when they were younger were no longer a factor. At this stage, I just wanted to make sure I was getting meaningful time with them and my wife.
Approximately six months ago, I was at a crossroad with Twitter. Unfiltered, it has become too toxic and negative to continue to allow into my life. My dilemma is that, after 11 years on the platform, there are a host of people I’ve never met “IRL” whom I consider friends or with whom I want to maintain a connection. Twitter has always been that connection.
What originally drew me to Twitter was an ease of interacting with a community of technologists and geographers, who shared tools, techniques, and knowledge. Over the years, as Twitter has “grown up” and captured the wider public imagination, in addition to changes in the behavior of the platform itself, the content of my feed has skewed more to the political and the negative – especially after the 2016 election.
This trend seems to apply regardless of ideology. People with opinions that span the political spectrum seem to take to Twitter to leave bite-sized and brash statements that bolster whatever position or candidate they support. In some ways, the structure of Twitter encourages this, even with the advent of longer tweets and threads as first-class citizens.
In the three years since the last election, I’ve become incredibly familiar (more than I ever wanted to be) with the political and social positions of a lot of people I follow, and not a single position has changed or evolved in that time. It has become a digital Forum Romanum, with countless self-styled tribunes shouting speeches into the passing crowd.
I didn’t need to continue to allow this in my life.
It is not the critic who counts; not the man who points out how the strong man stumbles, or where the doer of deeds could have done them better. The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood; who strives valiantly; who errs, who comes short again and again, because there is no effort without error and shortcoming; but who does actually strive to do the deeds; who knows great enthusiasms, the great devotions; who spends himself in a worthy cause; who at the best knows in the end the triumph of high achievement, and who at the worst, if he fails, at least fails while daring greatly, so that his place shall never be with those cold and timid souls who neither know victory nor defeat.
Theodore Roosevelt
I never met Ron Lake, but the majority of my career has taken place in the geospatial technology landscape he helped create. He is best known as the author and chief advocate of Geography Markup Language (GML), the XML encoding of geographic objects that underpins most of the Open Geospatial Consortium’s web standards and is a standard itself. This fact made him a pioneer, a visionary, and a source of controversy.
It is easy, for those of us who have worked with geospatial tools for a long time, to sit at a keyboard in 2019 and forget how much harder it used to be. By that, I mean working with geospatial data. It’s still probably more difficult than it should be, but it used to be so much harder.
It wasn’t that long ago that I was “always on” in terms of work. There is a certain ethos in the DC area that rewards that outlook and I was fairly good at it. This was compounded by the fact that I was a partner in my company and the buck always stops with the owners. Therefore, you always answered the phone/email/text/DM. A few years ago, I began to realize that this approach wasn’t serving me well over the long haul, especially in terms of my health.
What I needed to do was get reacquainted with discipline. Because I had fully bought into the idea that a business owner is never “off,” I had allowed discipline to atrophy. When all 24 hours of each day are available to accomplish tasks, then “close of business” means “before 11:59pm.” If you make your deliverable before the person you have committed to shows up for work in the morning, it counts.
There are obvious problems with this approach. First, work is always lingering in the background. Second, you are never fully engaged in any activity (including work). I coached soccer games, ran practices, and many other similar activities, but the block of code that I couldn’t quite finish before heading out to practice, or the proposal inputs due by midnight were never far away. Conversely the practice, or board meeting, or dinner party was always lingering in my mind when I should have been focusing on a proposal or my code.
My first management position was at a restaurant. It was a chain steakhouse in a one-horse town in Maryland. A few months into that role, I was the sole manager on duty for a weekend night shift that was going poorly.
Feeling my frustration mounting, I did the most mature and leaderly thing my 19-year-old mind could think of – I tipped over the break table, causing everything on it to crash loudly to the floor.
I felt a momentary rush of power as people scurried away from my obvious anger, setting off to do whatever they could do to right the sinking ship that was this shift. Word apparently spread quickly throughout the staff because, before I had walked another ten feet through the kitchen, I was confronted by a member of the waitstaff.
Louvre Museum [Public domain]
I forget her exact words, but they boiled down to “You’re being an idiot. This is your shift. If you want it fixed, go fix it or find another job.” She was right, and jarringly so. I’m pretty sure I didn’t fix that shift, but I never flipped a break table again in my restaurant career. Thus began a lifelong interest in leadership and management.
I should also note that, several years later, the woman who confronted me agreed to marry me and we will celebrate 25 years of marriage next year.
This blog started as my lifeline. Fifteen years ago, I was working on a project that wasn’t particularly compelling in an environment that wasn’t conducive to collaboration. I wasn’t doing geospatial work and I was worried that it would slip away. This blog was the mechanism that motivated side projects that kept me in touch with geography.
It started out as a technical outlet, with the intent of being the kind of blog that I often found myself searching for. From there, it evolved over time, though I fought that evolution for a while. Motivated by the same fear of losing my technical edge that caused me to start it, I kept a technical focus here even as my daily work became less technical. Eventually, I let that struggle go.
Perhaps because I know what my own thoughts were as I blogged, I can see that evolution unfold. Inadvertently, I ended up documenting the arc of a career in the geospatial technology industry.
Recently, I’ve gotten back in touch with .Net in the form of .Net Core. I’ve been shaking off some the coding rust and building some tools to help with data handling related to the Foresight data service at Spatial Networks. It’s been fun to get my hands dirty again and also interesting to see how .Net has evolved over the past few years.
It’s been a few years since I’ve done a lot with .Net and, after spending some time in the Node ecosystem, this was my first foray into .Net Core. The application I was working on just wasn’t coming together correctly in Node, so I started prototyping out the logic flow in .Net Core, with the intent to port it back to Node when I had a good reference implementation. The more I kept using .Net, the more impressed I got, so I just kept the application there.
