Not really applicative to the use-case of the main post, but I generally try to avoid name changes in code, at least when it comes to concepts.
The reason for that is that it has substantial benefits to have a clear and stable terminology to lean on, first and foremorst inside your team but also across teams and between developers and non-developers. Being lax with naming is a substantial contributing factor for misunderstandings, leading to plenty of bugs and loads of wasted time.
The main post if of course not about that, but about whether the use of certain words is socially advisable (even though there is indeed a side-case to be made about using clearer terms).
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Not really applicative to the use-case of the main post, but I generally try to avoid name changes in code, at least when it comes to concepts.
The reason for that is that it has substantial benefits to have a clear and stable terminology to lean on, first and foremorst inside your team but also across teams and between developers and non-developers. Being lax with naming is a substantial contributing factor for misunderstandings, leading to plenty of bugs and loads of wasted time.
The main post if of course not about that, but about whether the use of certain words is socially advisable (even though there is indeed a side-case to be made about using clearer terms).