hachyderm.io is one of the many independent Mastodon servers you can use to participate in the fediverse.
Hachyderm is a safe space, LGBTQIA+ and BLM, primarily comprised of tech industry professionals world wide. Note that many non-user account types have restrictions - please see our About page.

Administered by:

Server stats:

9.9K
active users

If you work with a database and are asked to alter the table structure to comply in advance for citizenship or gender categorizations it's really important to NOT do it.

"The governor is concerned about all this stuff they want us to update our record keeping so we store both gender AND biological sex."

"We need fields to store the country of origin of people's parents."

If you don't have the power to rebuff this yourself, ask for help. At minimum ask for help online anonymously.

Depending on your job you probably have in the past made compromises. Maybe to keep your job. Maybe to survive. This is a bright line. If you are asked to be the one to update the table don't let it be your fingers typing those changes.

If you can't just say "No I won't do that." Stall, run away, feign incompetence. Just don't let it happen.

I suspect this might be where the rubber hits the road first for us around here.

Nothing has changed. You do not have to do it. It is not even ordained.

Paul Cantrell

@futurebird
I would also suggest, if the refusal didn’t work, breaking the code so that wrong / random values get stored. Data corruption as sabotage.

@inthehands @futurebird

Add fields "genre" (Fr) and "genus" (Latin), set defaults to "dystopian surveillance horror" and "Homo" respectively, argue from etymology

It's a very specific kind of work-to-rule for linguists

@trochee @inthehands @futurebird Ha! Latin!
Field: Genitalia. Values: Penis, Vagina, Indutus

@inthehands @futurebird the ethical imperative to use C or fancy #C++ instead of #rustlang