I don't have any problem with the autocompletion feature.
However, I think being only able to work thanks to some tools / features can be a potential problem depending on your working environment context.
For example, let's assume you have an interview for a technical mission, and a part of your test consist of coding stuff. In such condition, the company could give you a machine without all things you are used to (as the autocompletion feature). If you only have been used to your "comfort environment", you could get stressed, lose some time and fail your interview.
Another "true story" example: last week, a developer needed some help for Git commands. Another one came to him, but they were not able to find their answers quickly because one wasn't using Git from terminal, but from its IDE. So he only knew how to do it with a visual interface, but not without its tool.
My point isn't that helpers are a bad thing, they are helpful actually :)
But I believe that being able to adapt yourself to any working environment by having some solid basic knowledges on how things work will help you even more.
I second this. Use the completions, and on a day when you're feeling expansive, figure out how not to use them.
I think of things like auto completion as scaffolding, not crutches. You put them up when you need them, and leave them up as long as they're necessary.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I don't have any problem with the autocompletion feature.
However, I think being only able to work thanks to some tools / features can be a potential problem depending on your working environment context.
For example, let's assume you have an interview for a technical mission, and a part of your test consist of coding stuff. In such condition, the company could give you a machine without all things you are used to (as the autocompletion feature). If you only have been used to your "comfort environment", you could get stressed, lose some time and fail your interview.
Another "true story" example: last week, a developer needed some help for Git commands. Another one came to him, but they were not able to find their answers quickly because one wasn't using Git from terminal, but from its IDE. So he only knew how to do it with a visual interface, but not without its tool.
My point isn't that helpers are a bad thing, they are helpful actually :)
But I believe that being able to adapt yourself to any working environment by having some solid basic knowledges on how things work will help you even more.
I second this. Use the completions, and on a day when you're feeling expansive, figure out how not to use them.
I think of things like auto completion as scaffolding, not crutches. You put them up when you need them, and leave them up as long as they're necessary.