My most frustrating professional experience so far was working in a sequestered program in my prior company where almost everyone in engineering leadership positions had been doing the same damn thing for 20+ years and could not understand why anyone would want to keep learning and trying out new technologies. In fact, showing too much interest in technologies unrelated to the program could be interpreted negatively.[1] I'm both amazed and horrified that such an attitude could persist in this day and age in such a company, but I guess that comes from the program's somewhat unique situation.
[1] The old guard on this program had the attitude that you could spend your entire career on it and its derivatives, so there was no reason to want to leave unless you were unhappy, in which case there must be something wrong with you.
I don't think this is indicative of the discipline as a whole. The discipline is necessary in many market segments. Even software companies have systems engineers; they just call them software architects. I'm not sure what could be done about a situation like I described above, though.
If you want to discuss this more offline, you can get my contact info from my profile.
[1] "Development" in this case was taking obsolete algorithm code, hacking in new functionality as quickly as possible, and forcing it to work with minimal perceived effort in the top-level system where all the software was being written from scratch.
It's not like technology or the rate of change will be slowing down in the future either.
So, learning how to learn efficiently is an important tech skill.