I kind of disagree. Our brains are very good at learning new words given the correct circumstances. Learning words is an effortless process that occurs through seeing them in context, and the nuance of having specific terminology is often extremely useful.

As a concrete example, if you say "I'm thinking slowly right now", someone might assume you have brain fog or some sort of trouble concentrating unless they've read a particular book. If you say you are using System II-thinking, they either get it because they've read that book, or they understand that they don't and can save themselves a lot of time and confusion and ask what you mean.

Using a simpler word for endianness does not spare you from having to understand endianness, but it might mislead you into thinking you do when you don't.

Re-using simple words can be confusing, and understanding that you do not not understand a word can actually be a feature, especially in technical writing.

As a good counter example, the word 'service' is used way too much in too many different ways. If someone says 'the service isn't working', they could mean the entire web application is down, the kubernetes Service-abstraction is misconfgiured, what it's running is broken, or some piece of code ending in "Service" doesn't compile.