GoKawiilI really appreciate that you're enjoying the software I'm maintaining and want to help. But we need to rethink this collaboration, because I feel like we're increasingly wasting each other's time.
Why I don't want to merge your PR#
Since I don't really know you, I always have to assume that you might be trying to sneak in something malicious along with your changes, which makes reviewing and merging them riskier than implementing them myself.
On top of that, there are a lot of personal and subjective aspects to code. You might have certain preferences about formatting, style, structure, dependencies, and approach, and I have mine.
Then we often need to synchronize with respect to review, CI runs, merge conflicts, etc.
And then there's this common back-and-forth round-trip between the contributor and maintainer, which is just delaying things.
Even before LLMs, writing the code was not the main bottleneck for me. But writing code did take time, so a solid, working, easy-to-review PR was often worth the small extra risk and inconvenience.
With LLMs becoming quite good at implementing things, that tradeoff is almost never true anymore.
While I still need to review LLM-generated code, I generally don't have to worry about it being malicious the way an unknown contributor's code could be. I've already codified a lot of my coding preferences and style guidelines for my LLM. And I can rapidly iterate at my own pace without having to synchronize with another human who might be in a different timezone.
For these reasons, it's just easier if I make the code changes myself (with the help of an LLM).
... continue reading