Users in this case would be other devs using the gender library. They should have enough technical knowledge to handle it.
You could also include common gender implementations in the library. Then we could start getting enterprisetm and include a GenderClassFactory that constructs Gender classes.
That’s not very user-friendly. And impractical for >99% of users.
Users in this case would be other devs using the gender library. They should have enough technical knowledge to handle it.
You could also include common gender implementations in the library. Then we could start getting enterprisetm and include a GenderClassFactory that constructs Gender classes.