I at least upvoted. This is the most level headed and sane reaction to this article.

Name checks out.

Extremely relatable post. I worked someplace that had a policy of absolutely never changing your Active Directory username because it was the primary key in like a dozen internal systems. Someone finally made a massive stink about it to HR when their name had legally changed but IT was forcing them to use their old name (and they were absolutely right to complain. It was a ridiculous policy only in place due to terrible architecture). They still defaulted to telling people no but they did at least document all the highly tedious manual steps necessary to change the name in all affected systems if (when) another employee refused to take no for an answer.

Was certainly a great lesson in schema design, among other things.

> You don’t use usernames as primary keys for anything, do you?

HAHAHAHHHAAHAHA

Seen this so many times I literally laughed out loud.

I too love folders with 200 UUID subfolders in them as well as URLs with 14 different UUIDs.

And what happens when you sync sharepoint to your windows files?

> Like usernames. You don’t use usernames as primary keys for anything, do you? What happens when people marry?

well it's extremly painful to rename the primary mail address or the UPN when it comes to microsoft 365 and active directory, especially in a hybrid environment. of course you can change upn's but it's definitly some kind of "primary key" for a user. in fact most systems at least use a UPN

> You don’t use usernames as primary keys for anything, do you?

Sure you do. Saves doing joins all over the place just to get someone's username. Makes hand writing SQL easier.

Apply head to desk.

omg