Angry Weasel Twenty-Seventeen Recap

It’s been a pretty remarkable 2017 for me – so much so, that it’s worth (for me) a little reflection.

This time last year, I had made the choice to leave Microsoft (but hadn’t told anyone yet). I went into work the week after Christmas (when nobody is there), and quietly cleaned out a bunch of personal stuff (I didn’t know if my resignation would be met with a “walk to the door” or not). Many of my reflections at the time made it into The Breakup, and the feelings that went into that post haven’t changed.

I officially left Microsoft in mid-January, and after a week off, began a journey at Unity that I have had absolutely zero regrets about. It’s been such a good mixture of problems I know how to solve (same movie, different cast), brand new challenges I don’t know how to solve, and wonderful, passionate people every direction I go. My new direct reports have all helped me so much in learning about the people and business at Unity.

In the meantime, I’m super-proud of the direction of the AB Testing Podcast, and how it’s helped me in my role at Unity (and how Unity have given me freedom to experiment using the principles of Modern Testing that Brent and I discuss frequently). Based on our vague plans for 2018, I’m even more excited about where our podcasting journey will take us.

I blogged a bunch of times – sometimes about testing, sometimes about Unity, and sometimes a combination. I also started the Five for Friday series which I hope folks find valuable.

I had a light speaking schedule in 2017 (although less light than the previous year where I was pretty much locked inside of Microsoft). I spoke at the Online Testing Conference, and then late in the year at Heisenbug. Next year is kicking off with three external talks in the first half of the year – that’s a bit more than I’d like to do, but an achievable task.

Back in July, I asked testers to join me in cleaning up the Wikipedia page on Software Testing. I think the page can be a lot more clear and reflect the state of the industry much better. While my contribution has been close to nil, it’s been great to see a few folks from the community step up and make incremental change. I’m not big on resolutions, but I do plan to play a bigger role in making the site a bit better for the masses in the coming year.

I’ve also had a chance to balance a hectic work schedule, kids with homework, and my own health. I began 2017 with a goal to run 510 miles (820km) (10 miles for every year of my age). While I thought it would be a slam dunk; I didn’t anticipate travel, live, and a month taking care of my dad in September. I made it to 480 miles though, and I’m confident that, barring injury, that I’ll make it to 520 easily next year. The good news is that since leaving Microsoft, the combination of lower stress and a bit more chance to exercise has dropped my blood pressure more than 10 points, and I’ve been able to lose 25 pounds (12kg).

I hope everyone reading had a fantastic 2017, and I hope we cross paths soon and often in 2018.

Similar Posts

  • The One That Got Away

    In case you missed it (because I only mentioned it on twitter), I have another article up on Sticky Minds this week. Here’s the abstract: Many testers have been involved in post-ship decisions about bugs that "got away"–bugs that escaped testing and found their way into customer’s hands. Often, these post-mortem discussions end up with…

  • Settling on Quality?

    Oh my – another quality post. I’m afraid I’m starting a trend for myself, but I have a story to share. As all gainfully employed workers in the tech field will tell you, we all have side jobs as tech support for all members of our immediate and extended families. This weekend, my mother-in-law opened…

  • Who are you?

    I’ve been thinking about how professional testers describe themselves. We have high level labels like Tester, SDET, or Quality Engineer, but beyond those (mostly meaningless) titles, many of us have our own personal missions or visions – the words we want people to associate with us. For example, my twitter bio is, “Long time software…

  • Unity

    For those of you who missed it on Twitter or in the AB Testing Podcast, my unemployment lasted (as planned) just a bit over week. On January 30, I started work at Unity, heading up quality for their various services. I spent most of last week trying to learn as much as I can and…

  • Five for Friday – October 9, 2020

    Not sure if it’s possible to find anything more interesting than Pence’s fly this week, but I tried. Mike Cohn wrote (yet another) article I enjoyed – this week’s topic asks, Are We Really Bat at Estimating? This twitter thread had some unsurprising thoughts (with some research) on the future of remote work. It’s now…

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.