I have now witnessed first hand what the unexpected benefits might be. I expected CC to be a boon to overburdened teams, because it's now possible to spend $2 on compute and have it write a mostly-one-off tool that nobody would ever otherwise have the capacity or time for.

Sure, that's happening too, but to a lesser degree than I thought. CC with a number of "enterprise integrations" (really: corporate MCPs) is a pretty hefty force-multiplier for operations teams. "Go summarise and dissect this weird client request for me. Documentation is spread across at least $THESE_ENTERPRISE_DATA_SILOES." Saves a bunch of time pinging the different people across continents who happen to know intimate details. That was not entirely unexpected.

It's the technically minded but not necessarily otherwise technical people who keep surprising me in weird and wacky ways. People are building themselves and their immediate peers disposable dashboards. Who needs a service to pull data for a real-time display when CC can collect the necessary information and construct a local, static HTML file with all the info neatly in one place? I'm sure there will be a hangover because the compute cost for doing these in JIT fashion will surely feel like death by a thousand cuts at some point, but the ability to really quickly validate whether certain types of data aggregations are useful is proving to be ... a positive development.

I disagree about the ease of maintaining the software, though. You still need the skills to really understand what the code is doing, and with the original "why" possibly lost in the adrenaline haze, the maintenance effort floor has shifted.