The thinking is, "if it ain't broken, then it ain't worth fixing." Unfortunately, recent advances by autonomous vehicle companies and EV makers have shifted the paradigm from a hardware-focus to a software one. I think construction is also headed the same path as stick-built buildings are increasingly on the way out and more modular preassembled manufacturing is coming in.
It's good news for software companies and bad news for traditional construction and traditional auto.
I'd love to be able to buy a new car without any software. My phone does anything I would want to be able to do in a car. But it's not possible, due to a combination of regulations and what the mass market wants.
Because really the reliability of software is much lesser than that of hardware (exceptions may apply).
Programmers speak programming languages. Common men speak human languages.
Incidentally, this is also why "AI" became such a big hit with the masses in such a short period of time: For the first time ever, common men can communicate with computers using human languages instead of programming languages.
Thats just a stereotype.
Lawyers speak legalese, managers speak managerial, electricians speak electrical, designers speak design languages, and politicians speak bullshit. And all of those languages can be employed/"translated" by "AI", there is no difference.
Or to put it another way, it all depends on the context. If you don't want to be understood by others you'll just come out as an asshole, and rightly so, whatever your profession.
Reducing such issues to “normal people can’t understand programmers” would be best left as a trope from the early 2000s.
If you don't see or understand the true value behind that, well, I suppose you're a programmer.
Was the same phrase used when compilers appeared? Or SQL?
As for why that is, well, you have to work in a non-tech company for a while to really see the problems. Suffice it to say that the gap between programmers and non-programmers in how they think and understand the process of developing software is enormous, and too large to bridge. You can't explain even things that would seem obvious and basic on this forum to non-tech people, because they just immediately reject it.