For our company’s fourth quarter (Q4, November 2022 to January 2023), I was the Acting Chief of Staff to CTO. In February, I’m getting back into my regular role as a Staff Support Engineer, while also spending a little bit of time transitioning anything left and ensuring any “loose threads” are tied up. Since there’s quite a bit to write about, and the role is so different from my regular role, I thought it deserved its own post. Continue reading “Reflection: Acting Chief of Staff to CTO at GitLab”
Tracking your work (for performance reviews and promotions)
People have often asked me about how I manage to put together summaries of my work (blog posts, performance reviews, promotion documents, etc.) in a relatively quick way, and the only answer I have to that is “I track my work.”
I’ve tracked my work for many years, well before working at GitLab, though what I’ve been using in recent years is the most comprehensive method I’ve used. I’ve had a lot of people ask me about it, so I knew it was time to write a blog post to share. Continue reading “Tracking your work (for performance reviews and promotions)”
Blog Year 2022 in review
Another year, another look at blog stats. So I say, but earlier this year, I did a summary from 2016-2021 since WordPress stopped generating them, and I totally forgot about it. In any case, here’s the 2022 in review. Continue reading “Blog Year 2022 in review”
TeamOps: Ensuring a Single Source of Truth (SSoT) at scale
Note: This was an “assignment” for TeamOps training, but thought I might as well post it here!
In small organizations, it’s generally easy to know what is the definitive source of truth since there aren’t that many places to look. Often, the source of truth is a particular document, or person. However, as organizations grow, different people or teams often remember or document the same things in different ways, and in different places. This is why it’s important to have a Single Source of Truth (SSoT). Continue reading “TeamOps: Ensuring a Single Source of Truth (SSoT) at scale”
Reflection: First third of my fifth year at GitLab and defining Staff Support Engineer
Normally, I wait until at least the half-year mark to do a reflection post, but this year for the 4th quarter, I am doing a rotation for the Acting Chief of Staff to CTO role, which deserves its own post. So, I’m doing the first reflection post now to cover mid-June 2022 to the end of October 2022.
If you’re a first time reader, you may want to read one or more of my previous reflections posts. Continue reading “Reflection: First third of my fifth year at GitLab and defining Staff Support Engineer”
Support Driven Expo 2022: Day 2 Notes
My notes from the second day at Support Driven Expo 2022. There should be more, but I missed taking notes for a couple of the sessions I attended before and after my own presentation. Continue reading “Support Driven Expo 2022: Day 2 Notes”
Support Driven Expo 2022: Day 1 Notes
My notes from the first day at Support Driven Expo 2022. There should be more, but I missed taking notes for a couple of the sessions I attended before and after my own presentation. Continue reading “Support Driven Expo 2022: Day 1 Notes”
Presentation: Everyone Can Contribute: Making Support Effective Through Contributions
Everyone dreams of talking to someone who can solve their problem. Opening up ways for Support team members to contribute to documentation and code will improve the customer experience and the company’s efficiency and we can prove it!.
Presented at Support Driven Expo 2022. Continue reading “Presentation: Everyone Can Contribute: Making Support Effective Through Contributions”
Reflection: Second half of my fourth year at GitLab and becoming Staff
Fourth anniversary! When I started at GitLab, I was wondering if I’d be here for 2 years, let alone 4 and counting. If you haven’t read it yet, I recommend reading the reflection on the first half of my fourth year though it’s not necessary to know what I’ve been up to during the last 6 months specifically, which is covered here. Continue reading “Reflection: Second half of my fourth year at GitLab and becoming Staff”
Summary and Thoughts on Being/Becoming a Staff Support Engineer
I recently organized an AMA on Being and Becoming a Staff Support Engineer. This was meant to be similar to last year’s Being/Becoming a Senior Support Engineer. Normally, I would have actually waited longer to do it, since I only got promoted in February and I feel like I haven’t been working at the Staff level very long. However, at the end of May, our other Staff Support Engineer, Will Chandler was transferring to the development team. So, I decided before he transferred would be a good time to have the AMA. Additionally, I invited Drew Blessing, our first Staff Support Engineer (who had transferred to development a couple years ago) to also join the group of people answering questions.
This is not just a summary of the answers from that AMA session though. I’ve tried to put the answers and thoughts together with the previous video that I recorded with Lyle Kozloff while I was still working on becoming Staff, and some additional insights. Continue reading “Summary and Thoughts on Being/Becoming a Staff Support Engineer”
You must be logged in to post a comment.