The <entity><has><attribute:value> pattern is actually a pretty powerful model. I think people often overthink their own situation, and just add more specific field names to their models. That's certainly fine when you KNOW the value will be used, but often attributes are optional, as your example demonstrates. So there's nothing entry-level about using it. It beats writing more code to accomplish the same thing, every time you want to add a relationship.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
The <entity><has><attribute:value> pattern is actually a pretty powerful model. I think people often overthink their own situation, and just add more specific field names to their models. That's certainly fine when you KNOW the value will be used, but often attributes are optional, as your example demonstrates. So there's nothing entry-level about using it. It beats writing more code to accomplish the same thing, every time you want to add a relationship.