I think software engineering gives people visceral feedback on principles/strategies that transfer well to other domains, but aren't as obvious to people in oth

I think software engineering gives people visceral feedback on principles/strategies that transfer well to other domains, but aren't as obvious to people in other domains. For instance: loose coupling, modularity, type checking, unit testing, avoiding side-effects, information hiding, readability, continuous integration, version control, service oriented architecture, reusability, many-eyes, (a)synchronicity, buffering, caching, portability, redundancy, fault tolerance, graceful degradation, avoiding premature optimization, rapid iteration, relational and object modeling, infosec, complexity analysis, scalability, technical debt. And, of course, any modern organization is totally dependent on software in some way, so understanding this stuff is always going to be helpful for a CEO when making related hiring decisions and signing contracts.