So much in software is badly named. Some labels or terms will never change regardless of whether they are well-named or not e.g. 'Pull Request' (see the links

So much in software is badly named. Some labels or terms will never change regardless of whether they are well-named or not e.g. 'Pull Request' (see the links below discussing this). Naming examples: - Product or service names that convey little or nothing about their purpose e.g. AWS (Amazon Web Services) - Well-understood dictionary words turned into fuzzy and imprecise computer science terms because no-one could think of anything better. Examples: 'composition' (as in 'composition over inheritance'). Or 'concern' (as in 'separation of concerns'). - Feature names, command-line names, API names - too many examples to list. But an interesting related article: Comparing confusing terms in GitHub, Bitbucket, and GitLab (2017) https://about.gitlab.com/blog/2017/09/11/comparing-confusing-terms-in-github-bitbucket-and-gitlab/ https://about.gitlab.com/blog/2017/09/11/comparing-confusing... - The GitLab link above was discussed on Hacker News. It includes an interesting first comment on the term 'Pull Request': https://news.ycombinator.com/item?id=11095652 https://news.ycombinator.com/item?id=11095652 - On a more sinister note: choosing words designed to obfuscate their purpose and to sound benign e.g. telemetry, analytics, web beacons. No company or developer would use the more honest label 'user tracking' would they? Finally, although every profession has a professional vocabulary, why does it feel that Computer Science is particularly amenable to the ugliest possible professional vocabulary? e.g. idempotence (not impotent!)