Synthetic inertia. Essentially, loads that you can quickly either shed or bring on in response to fluctuations. There can be a market for that too and that's what many grids are slowly discovering.
There is now increased evolutionary pressure for rules protecting scarcity to become norm. Communication media will likely adopt limits on the size and throughput of messages.
Love the enthusiasm but I don't buy the two macro tailwinds he's counting on: ever larger monorepos & more centralisation.
What you version together you build and release together, and there are architectural tensions pushing that size down. E.g. dependency indirection and change frequency. Mileage will surely vary by domain, but the idea that the "future is monorepo because agents" doesn't track with me.
The centralisation aspect has less to do with connectedness and more with topology, I'd say. Here, the agentic ways might actually push towards more hierarchical and distributed topologies than the centralised hub-and-spoke.
You're absolutely right, and I share the frustration.
I'm thinking a possible solution to this signal-to-noise problem is to embrace the longitudinal view: instead of comparing each scan with the normal across the population compare only against past self, unless there's a risk factor that warrants it.
This way we could presumably make use of plentiful scan data and mostly look at the stuff that evolves in suspicious ways, not what looks suspicious.
Don't "let it" generate tests. Be intentional. Define them in a way that's slightly oblique to how the production code approaches the problem, so the seams don't match. Heck, that's why it's good to write them before even thinking about the prod side.
- I'm not convinced the graph is necessarily cyclic. Often two codependents are actually dependent on some common bits and otherwise independent.
- this is essentially deterministic propagation of configuration (think dhall, jsonnet, etc) plus reconciliation loops for external state, terraform style — not dissimilar to how the rest of CI/CD should operate, in fact my view is this is an extension of CI/CD practices up the value stream.
I'm definitely strive for something like this when possible.