Maybe because programming in itself is not valued? Changing things with automation is, thus you need to have the right mix of domain knowledge and solution skil

Maybe because programming in itself is not valued? Changing things with automation is, thus you need to have the right mix of domain knowledge and solution skills to be successful. As these often are not found in one person (exceptions confirm the rule of course ;-}), you need a number of people collaborating. Appreciation for the "other" side takes time and can only grow with mutual trust backed up by joint success. Only pretending to know the domain and micro-managing into the "other side" is real and not helpful, as you wrote. This applies to programmers as well, they often mouth about how they know what would be best for the company and in reality just don't know all the constraints and background on the business side. Let alone how much of a social game creating software for others really is.