Comment by Ampersander

Maybe if you only use the LLM to proof read or something? I don't know if LLMs are actually any good for this purpose, but it's something I came to think of when trying to answer your question.

I do think that it is very difficult to not be a meat proxy when you utilize an LLM for writing tasks. These tools are computer programs that generate text, so what else would you do with it than have it write for you? This is being a meat proxy.

Trying to avoid being a meat proxy can quickly eat the supposed productivity gains of using an LLM in the first place.

Like say I need to write an article about some subject and it would take me the entire day to complete this task without an LLM. I can get some sort of article out of an LLM by simply asking, I don't need to think about the subject myself at all. The LLM productivity promise is also fulfilled, because I did an entire days work in a minute or so.

Now if I also need to read and understand the work, and be able to defend it or explain it to others as if I produced it myself, then this will take a lot of time. If on top of this I need to edit the text to sound like me rather than an LLM, then I probably still need the whole day for this task and I have lost all the productivity increase that I sought from using the LLM.

It's the thinking that takes time when you write, not typing. But you can't do the thinking and avoid doing it at the same time.

The same idea applies to coding too. Doing code review and requiring the author and reviewer to read and understand the code basically eliminates all the productivity gains that using the LLM was supposed to provide. Throw out the reviewing, reading, and understanding and we can have each developer producing a thousand kloc per day, over 1000x productivity. If we don't throw those out, we are comparatively in the exact same spot as not using LLMs at all.