“Some aesthetic reason” like cutting down on onboarding time? Making things a bit less complex for the juniors?
Standardization is more about consistency than aesthetics.
Standardization is more about consistency than aesthetics.
You: "I'm going to send a pull request"
Other engineer: "OK. BTW, we call them change requests here"
You: "OK"
Somebody else: Where I used to work we called them pull requests. Let’s have a meeting to discuss changing the terms to match industry standards. We may also want to create a committee to agree on other terminology changes too, like main instead of master.
And yeah, I've been in those long discussions too about frameworks and linting rules. It can often turn into just egos trying to win and less about doing what's right or expedient for the team.
If the workflow is different, then it's _not_ just a question of terminology. In that case it's probably a good thing that there are different names for the various workflows.