3 ms·
> Basically, I want to stop alienating project managers, product managers, and customers with weird jargon. The things you might need jargon for are things tha
by yorwba 9y ago
> Basically, I want to stop alienating project managers, product managers, and customers with weird jargon.
The things you might need jargon for are things that they shouldn't have to concern themselves with. If you use more familiar words but arrange them in unfamiliar ways, you'll cause the same confusion as by using jargon, except someone might believe they understood when they really didn't.
If you feel like you need to refer to programming concepts when talking to non-technical people, you're doing it wrong. Instead of talking about "immutable"/"constant"/"fixed", say that you made changes to prevent data from being altered accidentally. That's something they care about, not how exactly you did it.
- tyingq 9y ago>The things you might need jargon for are things that they shouldn't have to concern themselves with. Sure, but they become terms in titles of change requests, features, bug fixes, etc. It leaks out whether I want it to or not. And customers ask "what does this mean?" Or sometimes, forgivable but less polite equivalents.