So rsync rewriting all the tests puts the entire project in play. Now the entire protective surface has been sloshed through a layer of probability, so the loop must accelerate. Followup PRs add more carveouts with lengthy LLM justifications that sound perfectly plausible but amount to an erosion of the protective surface. We go from cumulative improvement to a random walk.
This is like a human cell goofing up its p53 genes and deciding that being cancer is good actually.
No, the answer isn’t replacing the test suite with nonfunctional slop and running it as root.
It’s all so amateurish and bizzare that my first thought was that someone stole the maintainer’s account. I guess nobody’s immune to the siren call of the slot machine.
It feels like someone being overwhelmed/exhausted to the point of saying “fuck it, I don’t care anymore” and afterwards rationalising the use of LLMs as the only way they can keep up, while simultaneously falling for it’s addiction. It does demonstrate why relying on one-man projects without chipping in is risky. Unfortunately the companies that rely on it are probably also captured by the bubble so they won’t think so.
Yes, people and companies should step up.
No, the answer isn’t replacing the test suite with nonfunctional slop and running it as root.
It’s all so amateurish and bizzare that my first thought was that someone stole the maintainer’s account. I guess nobody’s immune to the siren call of the slot machine.
It’s unjustifiable bullshit.
It feels like someone being overwhelmed/exhausted to the point of saying “fuck it, I don’t care anymore” and afterwards rationalising the use of LLMs as the only way they can keep up, while simultaneously falling for it’s addiction. It does demonstrate why relying on one-man projects without chipping in is risky. Unfortunately the companies that rely on it are probably also captured by the bubble so they won’t think so.
In the blog he posted afterwards he says he has 40 years of experience, so he is also grandpa old.