zlacker

Coding assistants copy your style to a fault. You got to be careful about things like typos in comments, or it'll start suggesting sloppy code as well. And conversely you have to be careful about overly bureaucratic conventions (doc comments for things entirely described by their name, etc.), or it will suggest overly wrapped hypercorporate code.

But used as autocomplete, it's definitively a time saver. Most of us read faster than we type.

>>vinter+(OP)
I assumed that was not what we were talking about, because I replied to:

> Personally, the chat UI is the main limiting factor in my own adoption, because a) it’s not in the tool I’m trying to use, [...]

though I haven't tried it through some combination of it the effort to set it up & it not particularly appealing to me anyway. The best it could possibly be would be like pair programming (back seat) with someone who does things the same way as you, and reviewing their code. I read faster than I type, but probably don't review non-trivial code faster than I type it. (That's not a brag, I just mean I think it's harder and takes longer to reason about something you haven't written, to understand it, and be confident you're not missing anything or haven't (both) failed to consider xyz.)