|
||||||
|
|
Inclusivity Matters By Richard Rost Addressing Feedback on Inclusive Gender Options I wanted to address some of the feedback I've received on my recent Microsoft Access video about adding more inclusive sex and gender options. Some of you have raised concerns, so I want to take a moment to clarify a few things. First, let me say that my goal with these tutorials is to create tools that are useful for everyone. This isn't about being "woke"; it's about recognizing that our world is diverse, and our databases should reflect that diversity. A Boolean field for gender may be efficient, but it's also limiting. Our goal is to make sure everyone feels seen and represented. To those who think inclusivity isn't important, I respectfully disagree. Many businesses, schools, and organizations are recognizing the importance of respecting gender diversity. Our tools should be user-friendly and reflect real-world changes. There's actual science behind this. Biologically, there are more than two sexes, and psychologically, gender is a spectrum. Many reputable studies support this, and it's important to create databases that acknowledge this reality. If you work for a company or are a private consultant, there will come a time when you will be asked to build a database to meet specific client needs. Whether or not you accept the job is completely up to you. You can either do the work or choose not to, similar to how some service providers may refuse certain jobs based on personal beliefs. The choice is yours. My job as a teacher is to show my students how to build their databases the way they want. And I will always choose inclusion over exclusion any day. If you feel strongly against this approach, I understand if you want to unsubscribe. But my aim is to help as many people as possible, and inclusivity is a core value for me. To those who support inclusivity, thank you for your positive engagement. Please continue to share your thoughts and constructive feedback. For those of you who don't support this, that's fine too. Build your databases however you see fit for your needs. Like I always say, they're your Legos. You play with them however you want. However, I will not tolerate any additional negative comments on my YouTube channel or website. If you feel the need to post bigoted remarks, know that you will be banned. Keep your negativity to yourself. Thanks for watching, and I look forward to creating more tutorials that help all of you. Live long, and prosper. RR
IntroIn this video, I respond to feedback about including more inclusive options for sex and gender in Microsoft Access databases. I'll talk about why it is important to design database fields that recognize the diversity of real-world users, address concerns about inclusivity, discuss biological and psychological realities backed by science, and explain why organizations are moving toward more respectful and user-friendly solutions. I also clarify my teaching philosophy and the standards for respectful discussion on my channel.TranscriptHi everyone, this is Richard Rost with Access Learning Zone. I wanted to address some of the feedback I've received on my recent Microsoft Access video about adding more inclusive sex and gender options. Some of you have raised concerns, so I want to take a moment to clarify a few things.First, let me say that my goal with these tutorials is to create tools that are useful for everyone. This is not about being woke; it is about recognizing that our world is diverse and our databases should reflect that diversity. A Boolean field for gender may be efficient, but it is also limiting. Our goal is to make sure everyone feels seen and represented. To those that think inclusivity is not important, I respectfully disagree. Many businesses, schools, and organizations are recognizing the importance of respecting gender diversity. Our tools should be user friendly and reflect real world changes. There is actual science behind this. Biologically, there are more than two sexes, and psychologically, gender is a spectrum. Many reputable scientific studies support this, and it is important to create databases that acknowledge this reality. If you work for a company or are a private consultant, there will come a time when you are asked to build a database to meet specific client needs. Whether or not you accept the job is completely up to you; you can either do the work or choose not to. Similar to how some service providers may refuse certain jobs based on their personal beliefs, the choice is yours. My job as a teacher is to show my students how to build their databases the way they want, and I will always choose inclusion over exclusion any day. If you feel strongly against this approach, I understand if you want to unsubscribe from my channel, but my aim is to help as many people as possible, and inclusivity is a core value for me. To those of you who support inclusivity, thank you for your positive engagement. Please continue to share your thoughts and constructive feedback. For those of you who do not support this, that is fine too. Build your databases however you see fit for your needs. Like I always say, they are your Legos, play with them however you want. However, I will not tolerate any additional negative comments on my YouTube channel or on my website. If you feel the need to post bigoted remarks, know that you will be banned, and I have banned a few people already. Keep your negativity to yourself. Thanks for watching, and I look forward to creating more tutorials that help all of you. As always, live long and prosper, my friends. I'll see you next time. QuizNo quiz available.SummaryThis message is a response to feedback about my recent Access Learning Zone video on providing more inclusive options for sex and gender fields in Microsoft Access databases. Some viewers expressed concerns, so I want to clarify my intentions and the reasoning behind these design choices.My main purpose with these tutorials is to offer database tools that serve everyone. This approach is not a political statement, but rather a recognition that our databases should reflect the diversity present in the real world. Using a simple Boolean field for gender may be technically efficient, but it fails to capture the full spectrum of identities that exist. The goal is to make sure all users feel acknowledged and represented in the software we create. For viewers who might feel that inclusivity in databases is unnecessary, I respectfully disagree. Many businesses, schools, and organizations are recognizing the need to be more respectful and accommodating of gender diversity. Our software should be both user-friendly and reflective of these evolving social standards. There is scientific support for this view. Biologically, sex is not strictly binary, and from a psychological perspective, gender exists on a spectrum. Reliable scientific research shows the complexity of this topic, and it is important to build databases that recognize these facts. If you are working as an employee or as a private consultant, you may at some point be asked to design databases with these requirements. Whether you choose to take on this kind of work is entirely your decision. Just as some service providers can refuse certain jobs based on their values, you are free to take or refuse projects according to your own principles. My responsibility as an instructor is to show my students how to build databases to suit their needs. For my part, I will always prefer including rather than excluding people through my work. If you are strongly against this kind of approach, I understand if you choose to stop following my content. My priority is to reach and assist as many people as possible, and inclusivity will remain a central value in my teaching. For those who support a more inclusive approach to tech, I appreciate your positive feedback and welcome your continued comments and constructive input. For those who do not agree, I encourage you to design your databases in whatever way fits your needs. As I often say to my students, your database is like a box of Legos: you can build whatever you want with it. However, I will not accept any more negative or intolerant comments on either my YouTube channel or my website. Any posts that are bigoted or inflammatory will result in a ban, as has already been done in some cases. Please keep negativity out of the community. Thank you all for your attention, and I look forward to continuing to share database tutorials that benefit as many people as possible. Live long and prosper, my friends. Topic ListThis is a response video addressing feedback about inclusivity in Microsoft Access tutorials, explaining the importance of offering diverse sex and gender options in databases and the instructor's commitment to respectful discussion and inclusive teaching. |
||||||||||||||||||||||
|
| |||
| Keywords: inclusivity inclusion gender sex PermaLink Addressing Feedback on Inclusive Gender Options in Microsoft Access |