From one rambler to another: I’m not sure who or what this aimed at, as it goes all over the place.

Cloud: Separating resources from what gets deployed is a classic separation of concerns.

I don’t miss the days where I had to negotiate with the IT team on hardware, what gets run, and so on.

Personally, I believe the next evolution is a rebalkanization into private clouds. Mid-to-large companies have zero reason to tie their entire computing and expose information to hosting third parties.

OpenAPI: The industry went through a number of false starts on formal remoting calls (corba, dcom, soap). Those days sucked.

The RESTful APIs caught on, and of course at some point, the need for a formal contract was recognized.

But note how decoupled it is from the underlying stack: It forces the engineers to think about the contract as a separate concern.

The problem here is how fragile the web protocol and security actually is, but the past alternatives offer no solution here.