Re: The complexity and scale of a proper corporate infrastructure
Back in the distant past - 1980s, 1990s - I worked in an environment where we had a small team working on Unix/RDBMS (mine), another on VAX/VMS and another on IBM type stuff all handling different aspects of the business. I'm not sure about the last two but in my area we didn't really differentiate between development and operations; our technical knowledge applied to both operations (which wasn't all that onerous) and development, and user support informed our knowledge of our part of the business which was essential for development. Back then it was just what we did - it didn't need a special name.
Only in the last few years before retirement was I in a mostly Windows shop where operations and development were separate. It made life harder, at least from a development point of view, not least because of the amount of ceremony involved in handing stuff over. Oddly enough the ceremony was suddenly set aside any time we had to look at the operational system to sort out the crap data my client's client (one of the Usual Suspects) had sent because their favoured Indian outsourcer had rotated in another lot of XML-deficient staff on short term visas.
I wonder if combining the two has somehow become special because of the notion that you have to crank out new stuff on a daily or even hourly basis.