A company I have visited had, for some obscure reason, decided that teams should have their own fun/memorable names. Almost 2 years after implementation, every new hire's first comment was: "it's impossible to navigate the org with those names, we have no idea of what each team is doing".
I could live with funny+descriptive, but for all that is good, funny only just does not work.
> HR that are completely oblivious to the idea that people have about them.
I can't imagine that's the typical HR pattern. That's certainly not better but I tend to think that they appear oblivious by design, or rather, by education.
Since HR must keep their smiling poker face and their never-promising aleays-optimistic discourse no matter what, they fake this seemingly oblivious character. I guess.
For me, it's hard to make good software today because the bar is actually higher, in the sense that it must be usable by a much wider audience and I can't be lazy about usability or even worse, let it unnecessarily complicated because "people should know about it or learn".
Because developer tools are increasingly polished and easily accessible without in-depth knowledge of the arcanes of the command line. And that's great to welcome more people in our field.
The downside is that once they're welcome, the climb of the learning curve is barely started.
That's a surprising statement to read. All your examples allow for statically significant unique identification (of a person).
I think that's where the threat actually lies. I'm equally worried about traces I leave with my Visa/MasterCard than those I leave with my uncovered face or fingerprints.
The main difference being that I can easily control the traces I leave with my cards, less so the traces I leave with my ohone, and it takes a significant effort to lkit traces from my face or fingers.
Excellent. This goes straight into my list of nice APIs for student work and coding exercises. If there's any way to contribute or support, you should advertise it.
Congratulations!