---
title: "human voice"
url: https://perrotta.dev/2026/08/human-voice/
last_updated: 2026-08-19
---


More and more I've been resorting to LLMs / Gen AI to file feature requests or
issues/bugs in upstream repositories.

Sometimes I get completely ignored, even when I follow the project guidelines.

For example, last week I filed [this
issue](https://github.com/earendil-works/pi/issues/7070) in
[Pi](https://pi.dev). It got auto-closed. I know
[why](https://github.com/earendil-works/pi/blob/main/CONTRIBUTING.md) it was
auto-closed, but it's lame, because I followed their guidelines. In spite of
writing it in my own voice, it got lost in the sea of slop issues. I can't blame
the maintainers, I totally understandand and sympathize with them. Yet, it sucks
for me[^1].

[^1]: And, frankly, for them too. I no longer feel motivated to file issues for
    Pi, even though I'm becoming a heavy user of it.

In other words: even when I put in the effort to file an issue manually, without
using an LLM, it gets mistaken for an LLM slop issue, because that's what
everybody else is doing.

Which kind of incentives does this create?

→ There's little reason to put in the effort to write issues in my own voice.

Which is, ironically, the opposite of what the project maintainers seemingly
hoped to accomplish (=to attract non-clanker contributors that file high-quality
issues).

So now I am pivoting.

I'll shamelessly create issues (or feature requests) with an LLM. I'll review
the wording first, but won't attempt to write them in my own voice. Would it
even matter? Maintainers are too busy and overwhelmed to be able to distinguish
slop from human voice, which is ironical — LLMs were supposed to _improve_ WLB,
not to make it worse. Oh well.

That said, pure Gen AI is lame. So I am starting to complement with a follow-up
comment in my own voice.

Today's example: [angristan/fast-resume#87](https://github.com/angristan/fast-resume/issues/87#issuecomment-5343487168):

> (human voice) **Disclaimer**: the previous comment was created by an LLM, I
> reviewed its text though. I can reliably reproduce this locally. I've been
> using `fr` [for a
> while](https://perrotta.dev/2026/05/fast-resume-search-coding-agent-sessions/)
> now, it's very handy. This is the only use case that is getting on my way.
>
> Let me know if you would like help to implement/address it. Thanks!

Check out [fast-resume]({{< ref "2026-05-25-fast-resume-search-coding-agent-sessions" >}}) if you haven't
yet. It's awesome.

I think this is a good compromise.