A person's name can change (and with a pretty high probability, will) once or more in their life
Cis men are the group generally least affected in our society right now, and this is one of those problems which would likely be handled much more smoothly if they weren't so overpowered in computer decision making.
Amen, this is why diversity is so important. There's nothing evil about being Cis and white but your experiences are not the experiences of everyone else. We may be the majority in tech but are certainly not in the world!
Not saying there is no truth in you comment, but I think there's a biased generalisation here, making it a matter of privilege.
I believe it is more a matter of either education and experience.
Developers (or decisions makers) of any category can't know every case, as they aren't machines; they'll do mistakes and oversimplifications. They'll almost always miss at least one use case; we shouldn't blame them for that.
I believe it's a limit of the industry as a whole, more than a social issue.
Designing in a more inclusive way is something that, I think, is more related to the responsibilities of a Domain Expert or a UX Designer; but the industry doesn't value those roles enough, or not yet.
In 10/20 years we might still have the same level of patriarchy, privilege and inequality, but I'm pretty sure it will be a lot more common to make inclusivity considerations while designing (either at UX, at domain or at technical level).
It's a matter of yet immature industry (a really young one, regardless of who make decisions), and of shared common knowledge and practices gained through time and experiences.
I would hope for improvement in team building and education, so that everybody is given the tools to be aware of issues that need to be addressed. So that everybody can share more wisdom to future IT workers and contribute to a better base of common practices to consider and remember.
To conclude I'll exemplify my point:
Personally I often complain of website assuming the user nationality or language, based on biased factors: my IP address won't reveal what language do I speak or what's my nationality, nor will my OS language, nor will half of my full name.
I don't make it a matter of privilege, but rather ignorance (that is: lack of exposure).
// , βIt is not so important to be serious as it is to be serious about the important things. The monkey wears an expression of seriousness... but the monkey is serious because he itches."(No/No)
I'd say there are other groups less "affected" than that one. In the "Privilege Olympics" there are many contenders.
The question here is about identity vs identification, and of the interests and independence of users vs service providers. Perhaps there are even implications for surveillance & mass control. But I think it's a stretch to characterize this primarily as a question of discrimination and diversity.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Cis men are the group generally least affected in our society right now, and this is one of those problems which would likely be handled much more smoothly if they weren't so overpowered in computer decision making.
Amen, this is why diversity is so important. There's nothing evil about being Cis and white but your experiences are not the experiences of everyone else. We may be the majority in tech but are certainly not in the world!
Not saying there is no truth in you comment, but I think there's a biased generalisation here, making it a matter of privilege.
I believe it is more a matter of either education and experience.
Developers (or decisions makers) of any category can't know every case, as they aren't machines; they'll do mistakes and oversimplifications. They'll almost always miss at least one use case; we shouldn't blame them for that.
I believe it's a limit of the industry as a whole, more than a social issue.
Designing in a more inclusive way is something that, I think, is more related to the responsibilities of a Domain Expert or a UX Designer; but the industry doesn't value those roles enough, or not yet.
In 10/20 years we might still have the same level of patriarchy, privilege and inequality, but I'm pretty sure it will be a lot more common to make inclusivity considerations while designing (either at UX, at domain or at technical level).
It's a matter of yet immature industry (a really young one, regardless of who make decisions), and of shared common knowledge and practices gained through time and experiences.
I would hope for improvement in team building and education, so that everybody is given the tools to be aware of issues that need to be addressed. So that everybody can share more wisdom to future IT workers and contribute to a better base of common practices to consider and remember.
To conclude I'll exemplify my point:
Personally I often complain of website assuming the user nationality or language, based on biased factors: my IP address won't reveal what language do I speak or what's my nationality, nor will my OS language, nor will half of my full name.
I don't make it a matter of privilege, but rather ignorance (that is: lack of exposure).
I'd say there are other groups less "affected" than that one. In the "Privilege Olympics" there are many contenders.
The question here is about identity vs identification, and of the interests and independence of users vs service providers. Perhaps there are even implications for surveillance & mass control. But I think it's a stretch to characterize this primarily as a question of discrimination and diversity.