this post was submitted on 13 Jun 2023
1 points (100.0% liked)

Experienced Devs

3961 readers
3 users here now

A community for discussion amongst professional software developers.

Posts should be relevant to those well into their careers.

For those looking to break into the industry, are hustling for their first job, or have just started their career and are looking for advice, check out:

founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[โ€“] tomcizek@programming.dev 1 points 1 year ago* (last edited 1 year ago) (1 children)

I was lucky I didnt faced this dumb attitude of locking others out of conversation. My experience from my early days is that seniors used jargon, but made sure that everyone understands what is means without any kind of shaming.

That's why I always considered jargon as useful. It is just some kind of model of point of wiew on some part of reality that we already agreed on (and must be clear to everyone in conversation). There is a saying "all models are wrong, some are useful". And critical thinking helps you determine if the presented model is useful in your context... or anywhere at all.

So I think it is good to understand some jargon, so you can determine if it fit your needs and brings any value, also you can be the hero who makes sure everybody understands.

[โ€“] terebat@programming.dev 1 points 1 year ago

Jargon is great for consolidating complexity into just a few words, reducing the things you have to think about. It can be equally valuable though to poke into implicit assumptions that are commonly made.

It's definitely a balance, and being inclusive in conversations is super important as you mentioned. It allows newer folks to get up to speed much faster in comparison, and allows more engagement across the people within the discussions.