Sigh. My career was in logical and enterprise data/information modeling. This was the kind of thing we constantly bumped into.
It takes a fair amount of time to learn about/appreciate the vast quantities of use cases and gotyas one needs to model for. Also for folks to really understand that logical and physical models are different and necessary. The stories I could tell...
Squeezing that into one week? I salute your effort!
@mcc Yeah, what bugs me are gender/sex markers.
It asks for gender, but shows sexes, or has a category error like, {male, female, non-binary}. Intersex is never listed.
As a transgender programmer, I have sought not to be that way, though I usually do B2N/interfaces, so I rarely end up doing anything with this.
@antiproton @mcc No no - it answers the question perfectly well :-)
Q: Why does the website care.
A: Marketing.
Q: So what should I put there?
A: Anything you like.
That's what me and all the other people born on 1st Jan 1970 think, anyway...
@TomF @mcc well I mean you can do that I guess.
I have an entirely offset, fake set of dates that I use. Like I said, the efficacy of their reasoning is necessarily suspect, but I think that's what it is. I've said in too many meetings listening to marketing people not to be suspicious This is the reason.
I'm just lucky that I don't have to code stuff like this normally. I don't do ux π₯°
@TomF @antiproton @mcc I used to always use January 1, 1900 -- so that it was very clearly a non-real birthday and that I was withholding information rather than attempting something fraudulent
Though recently some sites were no longer accepting that: I guess they have a maximum age check now (the current oldest known person was born in 1907)
So, I've started using January 1, 1920.
@TomF @antiproton @mcc Username & DisplayName, those are the only two pieces of information the site in the majority of cases should care about.
As well as some standard means of authentication (whether that be a password for forms or BasicAuth or a public key).
@lispi314 @TomF @mcc I mean probably, of course depending on what the site does.
I'm absolutely not advocating for the collection of data. One of my pet peeves is the inability for most companies to get gender and sex correct, and they usually don't need either one outside of some medical reason or something. Like I get why my doctor asks for it on the intake website.
@mcc As a programmer I strongly believe no computer program should need to know the gender of a user. It is the rarest of use cases in which this piece of information is relevant or useful at all - to facilitate the correct operation of a software.
If we accept the above, it might as well be treated as an optionally input free-form field. An indicator.
Only biz people want to know such metrics. For all the wrong reasons.
Programmers are not the decision makers in this matter.