Sometimes that's a yes, even if AI generated it and I can tell despite someone making half an effort to be a human for a minute during the PR process. But sometimes it's not.
It gets really dicey when you've kept an architecture a certain shape because there's a difficult feature you intend to slot into the negative space. There are two or three ways to implement that feature, and the one they chose just stomps all through your potential. But that's why we have code reviews. You don't have to read my mind if I just tell you. But it can be frustrating if someone asks you to do it a different way, and then has comments on how you accomplished that, and then comments on the fixes for your other comments.
My point being, docs were already an unsolved problem in code. Of course LLMs dumping reams of docs is not good, but are we really sure it's worse than before? Undocumented code is bad, and mis-documented code is the worst.
After reading the long verbose promising article, in the end, the guy (with the help of the agent) only managed to implement access to the PCIe config space so that lspci on the remote machine works and shows the remote PCIe device, but that's all. It never addressed the issues above nor even mentioned them. The code was AI generated. The article was AI-written. The article never made a reference to DMA, interrupts, MSIX-X, IOMMU, IOTLB, virtual memory, etc, but it made big claims on next-gen datacenter disaggregated architecture, boosting GPU utilization, reducing large scale inference costs, etc.
Anyway, you get my point: big long beautiful words, but zero nuance.