4 ms·

I think this basically doesn’t matter and it’s fine for institutional culture to have its own ingroup jargon. Trying to standardize for some aesthetic reason w

by c54 4y ago

I think this basically doesn’t matter and it’s fine for institutional culture to have its own ingroup jargon. Trying to standardize for some aesthetic reason wouldn’t add anything

jagged-chisel 4y ago
“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.
- Firmwarrior 4y ago
  I think most people would be able to handle any one of those terms smoothly on day 1 You: "I'm going to send a pull request" Other engineer: "OK. BTW, we call them change requests here" You: "OK"
  - allenu 4y ago
    If only it were that simple. As we’ve seen in this thread, you’d instead likely have: 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.
    - throwaway821909 4y ago
      I'm not sure if you're saying this as an argument for standardisation (ha, let's debate the spelling) or not, but these people will always find something, from frameworks to linting rules - the amount of discussion stays the same no matter how much is agreed
      - allenu 4y ago
        I'm not really arguing for one way or the other, just pointing out the reality of working with lots of people means lots of opinions on how to do things, so it's never that straightforward to get things done. It's just a fact of life. 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.
  - nfRfqX5n 4y ago
    The workflow is different enough where it does take some time to get used to
    - CogitoCogito 4y ago
      > The workflow is different enough where it does take some time to get used to reply 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.
PhasmaFelis 4y ago
I don't know that this particular term is a big deal, but it's a little alarming that you think standardized terminology has no more than "aesthetic" value.

by c54 4y ago

I think this basically doesn’t matter and it’s fine for institutional culture to have its own ingroup jargon. Trying to standardize for some aesthetic reason wouldn’t add anything

jagged-chisel 4y ago

“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.

Firmwarrior 4y ago
I think most people would be able to handle any one of those terms smoothly on day 1 You: "I'm going to send a pull request" Other engineer: "OK. BTW, we call them change requests here" You: "OK"
- allenu 4y ago
  If only it were that simple. As we’ve seen in this thread, you’d instead likely have: 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.
  - throwaway821909 4y ago
    I'm not sure if you're saying this as an argument for standardisation (ha, let's debate the spelling) or not, but these people will always find something, from frameworks to linting rules - the amount of discussion stays the same no matter how much is agreed
    - allenu 4y ago
      I'm not really arguing for one way or the other, just pointing out the reality of working with lots of people means lots of opinions on how to do things, so it's never that straightforward to get things done. It's just a fact of life. 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.
- nfRfqX5n 4y ago
  The workflow is different enough where it does take some time to get used to
  - CogitoCogito 4y ago
    > The workflow is different enough where it does take some time to get used to reply 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.

PhasmaFelis 4y ago

I don't know that this particular term is a big deal, but it's a little alarming that you think standardized terminology has no more than "aesthetic" value.