I wonder if the public appetite for the inevitable quality crash is there, though.
Uncaught TypeError: can't access property "parentElement", t is undefined
i https://io.google/2026/explore/workshop-2:29
<anonymous> https://io.google/2026/explore/workshop-2:29
<anonymous> https://io.google/2026/explore/workshop-2:29
Evidently the title is correct: we're beyond the tipping point of software quality.People who have never coded, for who we now need to spend an insane amount of time validating their design, asking questions they don't even have the answers to, figuring out if the code written was needed for the prompt or whether it was just thrown in there because ... the AI had it as part of the tokens.
Remember, their design isn't built from the ground up, it's focussed on the outcomes, like the movie Bedazzled.
And then you spend time validating their code, you give them review feedback, instead of internalizing it they just shove it into the AI and let it fix it, meaning they don't learn.
Next PR will have the same issues.
This reads like a bunch of marketing speak that says nothing.
It feels like Kubernetes? Yes, it allowed more complex setups but a decade later the leaky abstractions have become apparent and there are constant tradeoffs to be made with the problems it brings vs the problem it solves. But the awkward point is why was Kubernetes not a trillion dollar unicorn if it unlocked so much productivity gains?
Case in point: GitHub.