Understanding nomenclature is important

A reminder that, whenever you’re building something for someone else (a client, a business owner, etc.), make sure they are always telling you what they want with the exact words they mean to. Most non-tech folks will tell you what they want and how they want it to work, but we, as software developers, have to decode these words into a design system, and sometimes their incapacity of expressiveness forces us into having to choose how to name models, relations, actions and methods without full clarity on a given field. This can sometimes become a future tedious work when having to migrate from some naming convention to another when told that another term is preferred. That could lead to naming divergence between UI and infrastructure, or a full refactor to maintain consistency.