On the contrary, the software production value chain is fragmenting. On one end you have the hardcore mathematicians building things in Idris in the evenings (it's the future, right?), on the other the slick business folks with an arts background and enough experience to know where to steer the company/project/department. Neither wants to expend mental energy in the other's area of competence.
As software gets increasingly more complicated and moves up levels of abstraction, there is an ecosystem being created in the middle to bridge the two. A business-minded, but aware-of-computer-science middleman who translates from one end to the other, produces a clean functional spec from a messy, day long conversation with the user, or tells the CEO "sorry, that's not actually technically possible". One does not need to know category theory to be useful there.
Exactly the reason why I did a Bachelor in International Business Administration and a Master in Computer Science (Embedded Systems)! I feel that the gap in between is a good niche to be in. I have to say that there are some education programmes where the focus is on IT management that try to fill this niche too although I have some doubts about how effective it is to study IT management in itself.
As software gets increasingly more complicated and moves up levels of abstraction, there is an ecosystem being created in the middle to bridge the two. A business-minded, but aware-of-computer-science middleman who translates from one end to the other, produces a clean functional spec from a messy, day long conversation with the user, or tells the CEO "sorry, that's not actually technically possible". One does not need to know category theory to be useful there.