🫧 socialcoding.. @smallcircles@social.coop
Public

@unattributed exactly.

I practiced myself in avoidance of the term, and found that to be refreshing and lending a different perspective.

"Users" carries an aspect of depersonalization, but also implies an ownership relationship that creeps into the developers thinking, and even where the noble ones say "I serve MY users" it has consequences to the entire dynamics around software dynamics, and how the solution deliverable is able to serve the needs of different stakeholder groups.

Social experience design focusses on needs-based development and starts to consider problem statements first for all identified stakeholders in the solution delivery process.

For fediverse I use on occasion, the residents of the fedi universe.

🫧 socialcoding.. @smallcircles@social.coop
Public

@unattributed

Note that once you are conditioned to avoid the term "User" after a full career of addictive use of the word in that dev context, you start to notice how weird and awkward it really is.

You don't notice that while still addicted to your daily dose of saying "user" in broad generalization and technical abstraction. Devs think it is practical to use the word, pragmatic. But it is not. It is a technical word, and the use is similar to when a dev says "JSON" for instance. It is depersonalized, and that depersonalization seeps deep into the codebase over time. It is a word that anchors devs in the technosphere and keeps them there.

0
0
0

If you have a fediverse account, you can quote this note from your own instance. Search https://social.coop/users/smallcircles/statuses/116164017956040363 on your instance and quote it. (Note that quoting is not supported in Mastodon.)