[terom]

I do a lot of ops-ish work, and in addition to all the nice declarative configuration-as-code things where infrastructure changes are reviewed and applied in pull-request form, there's a lot of ad-hoc debugging/diagnosing and one-off changes that get done.

I totally over-communicate on everything where I'm debugging or mutating the actual shared infrastructure. In some places, this is literally in the form of displaying all `sudo` logs in-line in the IRC channel. If I'm debugging some issue, I'll be copy-pasting links to google results, screenshots of the the monitoring graphs and any diagnostic command output into that slack thread. Once I figure it out and either run some one-off commands or make a PR to fix it, I'll include those in the the chat. If I typo some command and (almost) make a mistake, I'll certainly mention that as well.

It's a real-time log/diary of the investigative process and any changes. These slack threads are typically solo threads, with just me replying to myself. This is fine. Occasionally other people will comment on something, occasionally I'll be searching for and referring to those threads later on.

Stuff that I'm working on solo and isn't leaving my laptop outside of a `git push`? Not necessarily worth mentioning before it hits GitHub, but please spend some time and write a useful PR summary.