There’s also a part in the denouement where he says a possible solution to improving slop code quality and safety standards is uploading the code to public repositories so similarly inclined people can engage with it
Which assumes people actually want to deal with slop code. An assumption that can be proven wrong by simply looking at the slopnami's effect on the open source ecosystem. Speaking of which:
which, I don’t know, seems kind of familiar if you’ve been a programming adjacent for two seconds. But then you’d also be aware what the slopnami is already doing to the open source ecosystem.
Honestly, I'd be willing to bet good money on the ecosystem's collapse at this point - the slopnami has tanked software quality across the board, the plague of scraping has made sharing source code deeply unattractive, the flood of LLM bug reports has crippled FOSS's ability to find and fix bugs/vulnerabilities (which combos nicely with LLMs increasing bugcounts), and, as Baldur's noted, the labour surplus FOSS relied upon has gone down the shitter.
On top of that, senior devs are burning out and deciding to GTFO en masse, and junior devs are getting deskilled, burnt out and/or laid off, crippling FOSS's ability to replace any maintainers they lose.