An Interlude

As you may have noticed, I’ve had to take a bit of a break from blogging. I’ve kicked out at least a post or two a week for a few years now, but I’m not dry on ideas, and I definitely want to follow up on my recent Test This post (before a follow up becomes irrelevant).

The challenge is that my day job is kicking my ass. I expected the UCIF test and certification work I’m involved with would take about 20% of my time (actually – they told me to expect 20% – I was hoping to get away with a bit less), but lately it’s been making a much bigger dent in my work day. Currently, I’m preparing a progress report for the board, and a members only webinar for later this month, along with trying to gain some ground on the roadmap for the working group.

The Lync team is bearing down on an internal milestone and there are a lot of loose ends (both technical and pseudo-political) to tie up in the next several weeks. Yearly performance calibrations are going on at the same time, so along with my normal levels of coaching and mentoring, I’ve had a few extra sessions of tester therapy in the past weeks.

And then there’s the not-really-work stuff that I still need to do. Top of the list is finishing my PNSQC paper, and I’m also juggling and negotiating some potential speaking engagements for the fall. For the first time ever, I’ve also had to start saying no to some internal speaking requests (sorry – if you read my blog, I hope you ask me again later this summer).

So – once I find a light at the end of the tunnel (or when the day job finally breaks me), I’ll be back.

Similar Posts

  • More Tester Exploration

    A few days ago, I began a verbal exploration of testers who code and coders who test. That post provides some context for today’s continuation, so if you have a moment, go ahead and check it out. OK – I know you didn’t read it (or you read it already), so I’ll give you the…

  • Tester DNA

    In HWTSAM, we (Ken, actually) talked a bit about tester DNA – that bit of mental goo that makes some people better (or at least more prone to being) testers. As I’ve been talking to (potential) testers lately, I’ve had a chance to dwell on this a bit more. What is it that makes a…

  • This week’s conference

    Every year, Microsoft’s Engineering Excellence group holds an internal conference – five days of talks, panels, booths and receptions (in other words, it’s just like any other conference, except only Microsoftees are invited). This is the first year since 2004 where I’ve been at the conference and not in the EE group. You’d think that…

  • Activities and Roles

    I’ve been thinking about testing activities and tester roles lately, or more lately, since it seems to be a recurring topic on this blog. I have to admit that I remain a bit surprised how often testers argue about what is and what isn’t testing. So – let me throw a few examples of potential…

  • Five for Friday – February 15, 2019

    Another week, another random five things I found interesting. Feedspot.com lists AB Testing in their top 10 software testing podcasts. Although it has “Testing” in the name, my 2019 goal is to get AB Testing into more Agile or Software Development podcast lists. Joel Montvelisky, who is one of the three AB Testing listeners is…

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.