External Publication
Visit Post

Anti-LLM Sentiment Considered Harmful

Haskell Community [Unofficial] May 6, 2026
Source

I posted the below comment (reporting on how I use LLMs) on another thread, without realizing that this one existed:

How to filter out vibe-coded dependencies

I use Opus to generate almost all of my code these days … bounded, however, by structural review enabled by srid/agency.

The last few PRs in Emanote are all generated by Claude Code.

I’m clearly on the pro-LLM side, but I can relate to one point from the anti-LLM site — which is the review overhead. When a contributor opens a PR that was LLM-generated, why should I accept it when I could have done the same myself (especially near-autonomously using srid/agency?). I don’t know the answer to this; an idea I came up with was to encourage contributors to submit elaborate proposals instead (see kolu and the example PR), which—once finalized, based on human discussions—can be fed directly to LLMs. The contributors contribution will be the proposal & spec that still gets record in the repository.

And LLMs do generate ‘average’ quality code. Not to mention, architecturally weaker one. And they are not creative enough to identify opportunities to extract frameworks or libraries out. All of this still requires the human in the loop, even though I believe it is possible to automate some of this in the future.

Discussion in the ATmosphere

Loading comments...