upvote
Maybe we can also replace the customers with agentic consumers.
reply
> The forceful executive, Henry Ford II, and the leader of the automobile workers union, Walter Reuther, both saw many examples of advanced machinery operating at the plant. The words they exchanged brilliantly encapsulated the paradox of automation:

> Henry Ford II: Walter, how are you going to get those robots to pay your union dues?

> Walter Reuther: Henry, how are you going to get them to buy your cars?

https://quoteinvestigator.com/2011/11/16/robots-buy-cars/

reply
I think you're being sarcastic, but there is actual truth behind what you're saying.

Because every developer is now a slop cannon by default, by default users will experience churn and whiplash, and things will break all over the place. As you point out, this is bad. It's also impossible to fix without deploying agents on the QA side. Like it or hate it, agentic testing is inevitable to protect users from the churn and noise caused by the slop cannon. I don't think that replaces test engineers at all - if anything it makes the job more fun. If you've ever had to keep playwright tests in sync with the target manually, and kept the CI environment up to speed with toolchain changes, you know what I mean.

Whether the "slop cannon by default" situation could have been avoided in the first place, is another question... But we're here now and there's no going back. Might as well deal with it as best as we can.

TLDR: it's not all bad :)

reply