[thethirdone]

> e.g. I use the terms "Flag" instead of "Boolean" and "List" instead of "Array"

It some cases "Flag" makes much more sense than "Boolean", but when using logic gates does "Flag" make any sense? Wouldn't it make people think of actual flags more than an on or off signal.

"List" and "Array" mean different things in CS. Lists cannot be accessed arbitrarily whereas arrays can be.

> One can get pedantic over the exact meanings of symbols, but during the actual act of programming, simpler terms can help reduce friction.

"Simpler" is a matter of perspective. Any experienced programmer should not have any problem with Arrays vs Lists vs Queues, etc, and they are all necessary concepts to be able to talk about and program with.

Most jargon exists because it is able to describe things that are not used in everyday life much more efficiently than without it.

[liamzebedee]

Depends on the context. If you're writing a CRUD web app with simple business logic, is the mental priming of data structures like arrays relevant helping you develop?