This post was “written” almost a year ago. I was experimenting with using dictation tools to write a post on my morning walk, and the end result was pretty scattered and required a lot of editing. I got about half way done, had to move on to other things, and promptly forgot about it. This morning I stumbled across that draft in progress and decided to finish it up. Honestly, it was rough. I had to remember what was on my mind a year ago, and I went off on some completely unrelated side rant that was about a thousand words long and needed to be edited out. I think the end result here is worth posting, though, so here it is.

The company I work for recently went through a major reorganization. A new department was created for our business unit and our team was moved into a new vertical under a different executive. A VP position was created to head up the new department, and another senior leader was given that position to help align all of our Agile/Lean/Project/Strategic activities.

It’s a lot of change. I was, admittedly, quite shaken when it happened. I’ve had my cheese moved more than once at my current job, but this one felt overwhelming at first. I don’t feel that way any more, and in fact I’m really excited about all the changes, but that initial jolt was pretty big.

One of the reasons it was such a shock to my system is because I was moved into what we are calling the “process” vertical in our organization. As someone who believes in and supports Agile, being in a group that seems to be on the “processes and tools” side of the “Individuals and Interactions” equation wasn’t a look I was happy with. I’m still not entirely keen on the optics around it, if I’m being honest, but I do believe that in our current structure we landed in the right place.

In any case, I was meeting with my new boss on Monday (the above mentioned Vice President of our newly formed department), and we were having one of many “getting to know you” style conversations we’ve had since the change. While we’ve worked together for many years at this point and have a perfectly amiable working relationship, we don’t really know each other all that well so we’re spending some time working on that. In our conversation on Monday, he asked me where I wanted to be in five to ten years.

Now I need to go ahead and state for the record that he knows about my cancer and said right up front that he realized his prepared topic for the day probably wasn’t something that was top of mind for me at the moment. I concurred and stated that “alive” was really my top-of-mind goal, but since I intended to achieve that one it was totally cool to talk about what else I’d like to be doing and we did so. In the time that has passed I’ve thought about it some more, and that was the path I took to starting this post.

When I reflect on my early days in software development, I see a perfect example of how my mind works. My first job was with a company that sold ColdFusion based auction software. The original person who wrote the code did so in a way that was most efficient at the time he wrote it. The internet was slow, and any extra white space in the background of a page could cause longer load times, so he removed any characters that were “extraneous” from his code.

The result, while readable to a visitor of the site, was a solid mass of text that was nearly impossible to decipher on the back end.

As my responsibilities there grew I eventually got access to that code base and was charged with helping to fix/improve the software. Every time I had to access a page, I would poke around in it and make it better. I would add comments where none existed. I would explicitly name variables from x or y. I would tab-delimit nested code. I would update deprecated functions or replace code blocks that were inefficient. What I was doing was removing technical debt, but I had no concept of what that was at the time. I just wanted to understand how the code worked, and I wanted to help make it better.

Which is a perfect example of how I look at the world. I want to understand how it works, and I want to make it better. So when I think about where I want to be in five or ten years, my answer is really just as simple as that – I want to have made the world a little bit better. To do so I need to keep learning. To do so I need to look for ways I can improve the code of the world around me, whether that is in my personal life or professional one. I want to take my experience, my influence, and my knowledge and apply it in little ways to make incremental improvements for as many people as I can.

But, ultimately? I still want to be here.