I'm a classically trained violinist, and when learning there was a huge sense of "just follow the rules and the sheet music exactly until you get to composing".
In that sense, I think there's a lot of similarities to a lot of engineering practices. There's a straight line to follow on a lot of tasks, adhere to the rules and leave the magic/cleverness to the system architects.
When I switched to guitar, and subsequently discovered the world of prog/math metal, it felt incredibly freeing. However describing that kind of freedom to my friends who adhered to sheet music exclusively was a struggle. Polyrhythms, improvisation, playing by feel were blasphemous to that world.
In that sense I liken it to ratatouille. You must cook the recipe the master chef created exactly, and it's not our place to iterate and experiment.
As a software engineer, I see a lot of the same mindset often. There's a world of engineers who are rigid about sticking to the tried and tested way of doing things. There's nothing wrong with it, in fact it's very valued.
However you need the counterpoint. You need the innovative composers, you need the recipe creators, you need the system designers/architects. Having only one or the other is an imbalance.
I think that's what a lot of engineers get hung up on. Music is taught as rules.
but those rules quickly fall apart when you start having to account for feel, for emotion, for cultural differences etc... Things that aren't able to be captured in rules cleanly.