Sounds like they didn't think about the intended audience enough.

That's what I was thinking. Thanks for the info!

This is one of the things I wasn't sure about. I don't know if this source can be retrained or what. I wasn't sure what it meant to have it be open sourced. Is the model really only a few thousand lines? That is wild to me.

My concern is that while we have the code, we don't know what it was trained on or if they built any biases into that training data. I'm still learning about all this though.

Theoretically, yes. I'm sure this has a ton of eyes on it though. Give it a few weeks or months and anything in that repo will be reported on and either fixed or forked to remove the issue. That's one of the great things about open source. 1/

The only rule without exception is that every rule has its exceptions. I would never use uid. I would only use uuid if it was the actual name of the data type, never for a variable name.

You're good! I catch myself doing it all the time. It's an easy habit to fall into but my perspective has changed as I've gotten more experience and responsibilities. Once you work in the same code for years, the forethought starts to pay off.

Disregarding the conventions of the language or established team style guides, I prefer the lowercase d. No reason. In a vacuum, there's really no difference to me.

Nah. Use verbose and meaningful names. Code is read many more times than it is written and auto complete is in every modern editor. Readability beats code golf every time.