I was actually literally thinking about that as I worked on my solo project. This is like a coworker I can ask questions of and bounce ideas off of. It actually gives some insightful ideas. I was working on a file rotation scheme and it suggested naming the files uuid_<time in ms>_<resolution number> with the intent that resolution conflicts won’t need to be walked very often if ever optimizing the common case of file.0, file.1, etc. This isn’t like earth shattering or something I wouldn’t have thought of on my own, but it was something I would have a convo about and someone would suggest it and I would pause and consider and find value in it. This is beyond a reference material discussion, this is bouncing architectural ideas off of someone who knows their shit but occasionally hallucinates. That’s generally what I look for in coworkers and employees anyways.

Note: I’m aware UUIDs can contain the time but the intent was the UUID was invariant in the process and it would move to another file once it got to a certain size.