3 ms·
At a certain point, it makes more sense to have a family tree diagram with alphanumeric labels for every possible relation cardinality referenced to self, and j
by akersten 5y ago
At a certain point, it makes more sense to have a family tree diagram with alphanumeric labels for every possible relation cardinality referenced to self, and just encode those as an enum like ContactRelationA4, ContactRelationB1, etc. And just point people to the diagram.
The Apple way is just long, impossible to parse (whose Father?) and in general pushes a lot of code smell buttons for me ("not sure what it is, but I'm dang sure it's rotten")
- hn_throwaway_99 5y agoI disagree, though I think a more intuitive name for this would be CNLabelContactRelationYoungerFemaleCousinWithDifferentSurname.
- jon-wood 5y agoYoungerFemaleCousinWithDifferentSurname is encoding a lot of assumptions about how familial relationships work in Western European/American cultures. Looking at all the possible values in that enum to me doesn't scream of a massive code smell, but instead of years of care and attention being given to proper localisation for often wildly different cultures.
- thaumasiotes 5y agoI suspect the relationship is not labeled differently if the surnames are identical by coincidence. (There was once a taboo against two people of the same surname marrying, but it can happen today.)
- vitus 5y agoI actually have an especially weird but related case in my family. My sister married someone whose surname is the same as my mother's maiden name. His mother's maiden name is the same as my surname. One of our parents' first meetings was to get together and make sure they weren't related... But in particular: how do you distinguish between second cousins in that case? (The term in question isn't limited to first cousins, after all)
- forty 5y agoOr maybe CNLabelContactRelation表妹 ?