A look at how most database schemas from the 1950s through the 1990s were designed to encode gender as a binary, reinforcing the social norms from that period
College student Manahil Bandukwala recently tweeted a complaint about her computer science class.
Context & Ripple Effects
The spark was small: computer science student Manahil Bandukwala tweeted a complaint about her class, and Slate turned it into a look at how schemas built from the 1950s through the 1990s hard-coded gender as a binary value. The point is that these aren't neutral leftovers — they're artifacts that still misclassify non-binary people every time a legacy system demands an M/F answer.
The story slots into a documented arc about whose norms got baked into computing: a field once treated as "women's work" until women were systemically pushed out in the US and UK, a culture whose sexist undercurrents turned Silicon Valley into a brotopia, and a gender gap already visible at the dawn of the web boom among Stanford's class of 1994. A binary enum in a decades-old table is that same history, persisted to disk.
First-order effects
- Non-binary users remain misclassified by systems whose schemas offer no representation of them — the direct, ongoing harm Slate documents.
- Bandukwala's complaint puts CS instructors on notice that schema examples taught as convention carry social assumptions worth interrogating in class.
Second-order effects
- Organizations maintaining legacy personnel, customer, and government databases face pressure to budget schema migrations and form redesigns, since the fix lives in old code rather than new policy alone.
- Vendors and institutions competing for students and recruits — the same pipeline Wired found alienating women in university recruiting sessions — gain an incentive to show inclusive data practices as evidence they've changed.
Third-order effects
- If the scrutiny spreads, data modeling gets reframed as a values-bearing act: reviewing what fields encode becomes part of inclusive design the way accessibility audits are, and standards bodies face calls to deprecate binary gender formats rather than inherit them by default.
The trend: Technical defaults inherited from mid-century computing are being re-examined as cultural artifacts, pushing inclusion debates from interfaces down into database schemas.