Craig Miskell README

Craig Miskell, Staff Site Reliability Engineer, GitLab

What I work on

Anything FOSS. Windows literally gives me a headache (when I previously had to occasionally deal with Windows in more than a passing manner I would usually have a headache at the end of the day); it simply doesn’t work how I want computers to work, and it hurts. Otherwise, I’ll give anything a try; if I can start with installing it and then work my way down the various layers into the source code until I’ve made it work or found why it can’t work, I’m happy.

I particularly enjoy weird/strange/complicated technical issues, so if you’re stuck on something strange and have no further leads to follow, or are out of time on something urgent, I’ll be delighted to help (subject to availability). I have a dream of one day opening a consulting business focused solely on debugging the weirdest edge case problems, with a sliding scale of fees that gets cheaper the more interesting/weird the problem is and the more I can publish about the investigation, whereas if I can find the answer on the first page of my first Google search, the fee is astronomical. I may need to win the lottery first to fund it, but it’d be lots of fun.

Specifically at GitLab I’m in the Dedicated Group where we build and operate GitLab’s Single-Tenant SaaS offering; as a Principal SRE there, my job is to provide support, guidance, and leadership on technical matters across the entire group. I sometimes even get to write my own code (/s).

Organisation

I use a local Kanban board to manage my immediate day-to-day and medium-term work. Todos and e-mails are, after initial filtering, turned into issues/cards on that board for Today; others (including random ideas that sprung to mind) may be in various ‘future’ categories from Tomorrow to Maybe Never

I strive very hard for Inbox Zero and GitLab Todo Zero. I consider unblocking colleagues one of my higher priorities, so I try very hard to respond to Todos that are blocking within a working day. If I haven’t responded in some manner within a couple of working days, I’ve likely lost/missed it and may need another prompt (and will be happy to receive it).

I subscribe to many relevant projects/groups in GitLab to maintain awareness of what’s going on, and as a result I get a lot of e-mails that I need to scan (and usually delete) quickly. Therefore, please @-mention me if you need a response or action, or think it particularly important that I’m aware of something, even if it’s a response to a thread I’m already involved in. Closing TODOs is quick and easy, and I’d rather do that a dozen times a day than miss important information or requests.

Communications

I prefer direct and unsubtle (but still kind) communication, and do not like having to guess what was intended, so I will generally assume the most obvious interpretation. If you want me to know something, tell me straight. In the other direction I aim to be similarly straightforward and precise in my word choice and phrasing, tempered by kindness. I both love and hate the English language; it is an awkward filthy language full of exceptions and weirdness, but there is a word, phrase, or idiom for everything, even if it was stolen shamelessly from another language 300 years ago and thoroughly mangled in pronunciation and meaning since.

I welcome constructive feedback on how to do anything better; if I have made a mistake I prefer to know it so I can try not to make it again. In particular, I strive never to be rude or obnoxious (although I may fail on hopefully rare occasions), so if I am it is probably unintentional, and I ask that you tell me directly so that I can correct my future behavior.

If I’m at work (at my desk in my dedicated office), I tend to respond fairly quickly to Slack unless I’m deep into something technical. If I’m not at work (and not on-call), I occasionally open Slack on mobile but that’s a bad habit and I am trying not to. I do not have Mobile notifications enabled. I do not have any access to any other GitLab accounts (e-mail, gitlab.com, etc) outside my work laptop, which stays at my desk 99.9% of the time, and I intend to keep it that way.

Limitations

I speak fast sometimes, particularly when excited. If I’m going too fast (particularly with my NZ accent), please feel free to ask me to slow down and/or repeat myself.

I sometimes write too many words when fewer would suffice; I’m getting better, but can still be far too wordy at times (even after the 3rd edit).

I can sometimes get locked into an indecision spiral from too many subtly different or conflicting options, but usually I am aware enough to ask for an external opinion and a little nudge will unstick me. If you think you see it happening and can unwedge me, please do.

Miscellaneous facts

  • I speak fluent GIF and emoji, and will often communicate reactions with those rather than actual words (which somewhat reflects my in-person communication style, which involves waving my hands about vigorously).
  • I live in New Zealand so my timezone is NZST/NZDT (GMT+12 or GMT+13), and my usual core work hours are 08:00 to 16:30. I can potentially be available from 07:30 with sufficient prior warning, and can be coherent up until around 21:00. Exceptions can be made when necessary, but I pay the price afterwards. Or: I’m good in the morning, and not so good at night.
  • My pronouns are He/Him
  • When I’m not working I:
    • Play Factorio; I used to play it far too much, now I’m past that and can usually only play it for maybe an hour at a time before I get twitchy and have to stop. This is good for me, particularly for getting other things done
    • Make music; long-time piano player, self-taught bass guitar, and now learning the Double Bass since early 2021.
    • Bake treats, preferably when I can give it away, otherwise I eat far too much of it myself.
Last modified December 14, 2023: Move Craig Miskell's README to GitLab (aaeff010)