When I was writing code for a medical facility, the guy who designed the database was as straight-laced and socially conservative as you'll meet.
But his design handled same-sex marriage/bigamy/polygamy/transgender issues, etc.
(It was a mental health facility. You get all sorts of interesting data problems when tracking the outliers.)
His philosophy on the design --and I'd imagine this isn't so odd amongst geeks-- was that data was data and needed to be tracked in a proper and robust manner, regardless of rightness or wrongness or personal feelings.
Assuming a male/female table is a reasonable logical starting point because 'some people feel this way' is akin to suggesting redundant christian/muslim/dirty_atheist tables would/should be expected to occur in professional code, because 'some people feel this way'.