Long ago we had product builds that took hours and tests that often ran overnight, and sometimes over days. And I miss those days as well. I think the author'

Long ago we had product builds that took hours and tests that often ran overnight, and sometimes over days. And I miss those days as well. I think the author's point was not a wholesale dismissal of the value of extensive testing, as such. But rather - whole point of a CI/CD pipeline is that you're supposed to get the feedback ... reasonably fast, right? That's what the "C" is supposed to stand for, pretty much (along with adjacent matters of being explicitly tied to your commit/merge process). So they aren't saying there's no value of all that testing -- but rather, if it takes hours and hours (when it was supposed to be nearly synchronous with your commit process) -- its values does attenuate. Or if you're spending resources making it faster - rather than figuring out what's wrong with your code or models in the first place - that's another tax to pay.