Paul Zuradzki
Vicki BoykisI've come across this naming issue in software a bunch recently: I have a machine learning model, an object model (Pydantic for example), and an MVC model. How do you disambiguate between these different taxonomies in your code?
Madame Pres commandasaurus 🦖@vicki I would like to subscribe to this question. The word "model" is so over-subscribed now that I always have to ask what the context is for further discussion.
Federico Mena Quintero@vicki Use different cases: Model, mOdel, moDel.
Use acronyms: ml_model, o_model, model_vc.
Give the names: mlm is Skynet, om is Gary, mvc is Jackie.
Plan for expansion: model_1, model_2, model_3.
@federicomena perfection
ck
Karl Higley@vicki I’ve started calling object models “domain concepts” in order to avoid that ambiguity on a current project. Feels a little awkward, but does emphasize an aspect that makes us think a little harder about the distinction between the domain and the format external data happens to come in.
@vicki curious to see how folks handle naming “models” too. For me, I use namespace or prefixing. E.g., if I’m using both a domain object and related ORM model managing a related table but I want to DB to be decoupled from biz logic, then both domain and ORM models are either namespaced (e.g., domain.py:Patient vs Django models.py:Patient) or I might prefix like `ORMPatient` and `Patient`. Latter is arguably more explicit but kinda ugly.