As a dev I would refer to the people running my software as users all the time, a user runs software under a user profile with their limited user privileges, we might write the user data to the user home directory, identity them on the backend by some user id but probably want to use the user display name on the UI.
Its not derogatory but when your implementing the software the user holds a distinct role and is perfectly valid terminology for the person using the software.
User to me falls in a similar category to “client” or “customer”, none are derogatory, but they’re all very transactional. “Fan” or “gamer” feel more familiar, like a hotel “guest”. It’s a minor distinction, but it implies more of a two way relationship, and from personal experience, the language used by leadership tends to closely tie to how employees treat their customers.
As a dev I would refer to the people running my software as users all the time, a user runs software under a user profile with their limited user privileges, we might write the user data to the user home directory, identity them on the backend by some user id but probably want to use the user display name on the UI.
Its not derogatory but when your implementing the software the user holds a distinct role and is perfectly valid terminology for the person using the software.
User to me falls in a similar category to “client” or “customer”, none are derogatory, but they’re all very transactional. “Fan” or “gamer” feel more familiar, like a hotel “guest”. It’s a minor distinction, but it implies more of a two way relationship, and from personal experience, the language used by leadership tends to closely tie to how employees treat their customers.
That was what I was trying to convey thanks for being better at words haha