Last week I was at corporate HQ, where the rest of my group is, for a few days. Everything about the trip in on Monday was a model of efficiency -- the plane got in early, getting off the plane was faster than usual, Uber came right away, traffic was light -- so I got to the office about half an hour earlier than any of us expected me to.
Given that, I was a little surprised to be greeted with "oh thank heavens you're here!".
The previous weekend there'd been a catastrophic power failure and many of our servers came tumbling down. (I didn't hear the gory details. We have what I understand to be the usual precautions, and yet...) The small team responsible for that infrastructure was understandably frazzled. My teammates were happy to see me because the (internal) documentation servers are not managed by that team but by us. But their main custodian, G, was on vacation, and another person who knows relevant stuff, J, was on vacation, and that left me. I know some of the systems well but not others -- which put me ahead of anybody not on vacation. Okay.
Our doc infrastructure team has two newer members, an experienced writer who joined the company last fall and a recent grad who joined the company last month and the infrastructure team a couple weeks ago. The former has been focusing on git as my backup, and the latter is solidly in learning mode.
So first we did the usual dance of "this is not the right dock for my laptop / these are not the right monitor cables / why TF can't Windows see both of these monitors? / network, we have network right?". Once I could actually use my laptop, I settled down to investigate -- with the two newer team members watching everything I did and taking notes. It was kind of like pair programming, I think. Read more…