I have seen what happens with garbage-in/garbage-out in databases, so this kind of stuff terrifies me. I often think of a case where we had a person listed twice in our database, with same address, birthday, etc, only thing different was gender, and last 2 digits of SSN were transposed..

After we 'fixed' the issue a few times, they BOTH showed up to our office.

Both Named Leslie, born on same day, a few small towns apart, same last name and home phone since they had been married. Back then, SSN were handed out by region sequentially, so one had the last two digits 12 and the other 21.

My uncle married a woman with the same first and middle name as one of his sisters. My new aunt chose to use her husband’s name as her married name, without hyphenation or anything. His sister, my aunt, never married. One was an RN and the other is an LPN.

They were born in different years. Their SSNs were not close. For one of them the name was her maiden name. For the other, a married name. They went to different colleges and had different credentials. They did live in the same town.

When my aunt died, all the credit companies and collections companies tried one of two recovery tactics. Some tried to make her brother pay the debts as her surviving spouse. The others tried to assert that the debts were incurred by his wife and that the mismatch of other data in their own databases was evidence of fraud.

I have two younger brothers. They have the same last name, first initial, a history of having lived at the same address, and the same birth date, because they're twins.

Every time one of them goes to a particular medical facility, he has to explicitly decline having them merge their charts.

That's funny as a human, amazing as a developer, and terrifying as a data processor. All at the same time.

I'll bet that pair has stories to tell.

Being married to someone with the same name could be very confusing!