> What the modern software business seems to have lost is the understanding that ops and dev are two different universes.
This is a fascinating take, if you ask me, treating them as separate is the whole problem!
The point of being an engineer is to solve real world problems, not to live inside your own little specialist world.
Obviously there's a lot to be said for being really good at a specialized set of skills, but thats only relevant to the part where you're actually solving problems.
Read some old o’reilly books on systems administration. Solving problems in a business domain and operating the infrastructure to support that are, indeed, very different. Urban planners needn’t understand how to orchestrate a bunch of heavy construction equipment and civil engineers needn’t care about how the sight lines affect the revenue of the stores in the buildings. They’re all building the same exact thing.
The issue is that precious few devs are actually good at ops. There are a ton of abstractions that have sprung up that attempt to paper over this, and they all suck for various reasons.
If you think you need to actually know your programming language of choice to be a good dev, I have news for you about actually knowing how computers work to be good at ops.