I seriously thought I was losing my mind this morning.

Loaded up my IDE and got to work.

Needed to find something in the project, so I hit the keyboard shortcut to find all usages in the project path.

The dialog pops up, but my selection is replaced with a long hex string. I thought it was weird, but I just installed the latest update of my IDE so I thought I'd found a regression. I grabbed the hex string and went over to Google to see if anything useful popped up.

The first result is the reddit post for my keybase key.

Wait. The "random" hex string was the fingerprint for my keybase public key? I double-checked to make sure that keybase wasn't running and I didn't have anything weird hanging out on my clipboard. Nothing amiss, but I still got my key whenever I searched for something.

This is the point where my brain got a little melty. I started running weird conspiracy theories in my head. My ever-helpful coworkers could only suggest to "stop using a Mac".

I saw that the app menu got highlighted when I opened the dialog, so I opened the menu and looked at the Services. Lo and behold, the GPG Suite update I installed recently very "helpfully" added a global shortcut to "Insert My Fingerprint" with the same keyboard shortcut as the IDE action.

Coworker: Hey, you made some changes over here in module X?

Me: Yeah. The old way was deprecated and we need to switch all of our modules over to the new way.

Coworker: Okay. I'm working in module Y now. When are you going to get to it and make those changes?

Me: ... I sent out an email and a message in group chat saying we all need to make these changes as we find them.

Coworker: Uh-huh. So when are you going to update this? It's blocking me.

How does a person get better at speaking in technical situations? I've been in the tech field for a loooong time now, but I really have trouble articulating my ideas. Someone else on my team can explain why our architecture isn't optimal because of X, and we should try to integrate Y because it buys us Z, and I usually can come up with some variation of "It sucks, because bad."

The things I want to say are generally the same as the person who makes sense, but my brain apparently has a disconnect between understanding it technically and being able to express it. I had kind of figured that by this time in my career I would have been exposed to this stuff so much that being able to talk about it would be easy, but it's not.

I've had Toastmasters suggested to me before, but I don't really need help talking in front of people. As long as I have time to prepare, I can do that kind of speaking with little trouble. I just want to be able to respond in meetings and informal situations and show that I do have a clue what I'm saying.

Our "agile" process uses one-month long sprints, ending on the last day of the month with a demo. (I'll rant some other time about non-consistent iteration lengths.)

Our sprint ends today (Monday). What was the most logical time to introduce changes that affect the architecture and break every single build? How about 4PM last Friday?

We're still waiting on the build breaker to show up while trying to figure out what the heck we can cobble together and run to show that we actually did something in the last month.