I’ve noticed something after using Copilot in VSCode for a while, which I’m also noticing now with the predictive code completion in Xcode 16. I will often feel like I’m being “interrupted” by the completion suggestion, especially when I already know exactly what I want to write. That interruption ends up being distracting and detrimental to my productivity. Anyone else notice the same?

I’ve resorted to disabling completions and just using ChatGPT to get help when I’m stuck (or just lazy).

@_inside There are times when it predicts exactly what I want, even once with some test data that I was creating. This impresses me and feels like magic. Then there are other times when it conflicts with what I’m thinking, or jumps ahead a bit more than I’ve thought through. Yes, then it’s distracting because I stop to wonder if I’m wrong or if it has a better idea than me. I’m going to leave it on for now and see if my brain learns to discern faster whether to accept or ignore.
@_inside I mentioned it here, too, and I’m glad to see now that others have the same experience. To be honest, I haven’t written much code this summer to see if my brain will actually adjust to this new tool. https://iosdev.space/@keithg/112686329325521744
Keith G. (@[email protected])

I’m impressed with the predictive code completion in the Xcode beta. I’ve been startled a few times when it knew exactly what I was typing. It took a little time to get over the eerie sensation, and then a little less time to accept the confirmation of my unoriginality, but now I’m excited by this tool. I do want to get better at knowing when to quickly accept the suggestion, and when to ignore the suggestion without getting distracted during those times when I’m not in harmony with it.

iOS Dev Space
@_inside I’m in love with predictive code completion. What I want is to get used to easly and quickly skip or accept the suggestion without letting it to interrupt my brain-fingers-keyboard code download.

@_inside Agreed.

My own hypothesis is that writing code, and “reviewing” code engages different enough parts of the brain, that mixing the two activities simultaneously isn’t sustainable.

Considering and potentially accepting these snippets is more like the latter activity, but I’m sitting at my editor to do the former.

@_inside Absolutely. I turned that off in a fit of pique in a day, but I use the ChatGPT app daily.
@_inside There's a all topic about the inverse called the "Copilot pause" where, even if you know what you're gonna type, you pause after the first words just to see if Copilot is completing what you want so you don't have to type it yourself.
@_inside Same here. I am still “exploring" the predictive stuff, though. Would I have to make the decision now, then I would turn it off.
@_inside I never used Copilot, but I've been using ChatGPT quite a bit to teach me rust, and it's super effective. Ended up using Safari's “Add to Dock" feature.
@_inside I’ve had it on long enough that I mostly expect exactly what it will autocomplete and I accept its suggestions all the time, I use it more than regular autocomplete at this point. Not sure how the Xcode one is.
@_inside yes! The autocompletions often get in the way. I should turn them off and just youse the chat feature directly when I need the help
@_inside yeah but I'm really quick with the Esc key, so it doesn't often distract me.
@_inside Yep sometimes I feel the same way, especially when writing doc comments. But I haven’t turned it all off because it’s still a net positive for me. When writing Ruby and Copilot completes a whole test after I write the description, it’s a pretty big boon.
@_inside I find the opposite lol, I end up getting distracted from the nonsense it tries to suggest and then lose my train of thought
@b3ll That is exactly what I’m saying though 🤔
@_inside OH crap my bad, I thought you were referring to Copilot doing things better. I agree, I've also yet to find something that has made me productive 🤝
@_inside took me a good while to get used to it. It’s still annoying at times, but I feel like most of the time I’ll just automatically hit ESC without being distracted too much nowadays.
However I like it enough when it works well to not disable it. That’s especially the case when giving it context e.g. via variable naming, or when doing „repetitive stuff“.
An option to set a greater completion delay would be nice though.

@_inside I just saw that @StewartLynch mentioned this recently as well.

https://iosdev.space/@StewartLynch/112917539909969016

Stewart Lynch (@[email protected])

I am finding that predictive code completion in Xcode 16 and Sequoia is just getting in the way. I am thinking of turning it off. Way too many predictions that get inserted into my code so I have to keep backspacing.

iOS Dev Space

@_inside yeah, it’s the same reason I’ve never been able to embrace pair programming. My brain works by assimilating the ‘problem’ and then compiling the ‘solution’.

I’m not so good at operating as an ‘interpreter’ where I have to simultaneously deliver output while continuing to assimilate more input.

@_inside that has been my experience with all predictive text or autocomplete or whatever the fuck for the past 15 years.
@_inside Agreed. I've ended up disabling completions altogether and just occasionally using the chat function. It's convenient that it's built in the IDE. But it's the only useful thing I got out of it, really. Copilot as a rubber duck (not a fellow coder) is sort of ok.
@_inside Yes! This is exactly the feedback I gave to my manager about my experience with Copilot.
@_inside same thing, there should be a bigger delay to some suggestions I think