5 ms·

> it breaks up flow much much less than having to go to the documentation all the time to look up minor naming variations (is it "start" or "begin"?). I read O

> it breaks up flow much much less than having to go to the documentation all the time to look up minor naming variations (is it "start" or "begin"?). I read OP's position as: If you don't use aurocomplete you'll remember the naming variations better, and won't have to look them up all the time. I still think aurocomplete might be faster for libraries you haven't used much before, but it doesn't sound at all unbelievable to me that the brain works as stated.

kstenerud 6y ago
I never used autocomplete until my fourth programming language. By that point, trying to write anything was an exercise in frustration as I constantly mixed keywords, namespaces and functions from the other languages. Nowadays, I just leave autocomplete on for minimal flow break no matter what language I'm using at the moment. I don't want language-specific names and structures interrupting the flow of models and ideas from my head.
snarfy 6y ago
OP's position doesn't work very well the more you generalize. I had OP's philosophy when all I was doing was low level C code. It doesn't work very well when you are switching between yaml, python, c++, c#, typescript all with different libraries, coding standards, and naming conventions. By the time you no longer need the reference to remember, the reference changes.
- svennek 6y ago
  For me, it works with 5+ languages I write (production) code in at least every month... I don't know how it is for others. Also, I really try to minimize complexity and not ending up in the javascript npm dependency spaghetti.. Good code is simple and obvious....
svennek 6y ago
> I still think aurocomplete might be faster for libraries you haven't used much before, but it doesn't sound at all unbelievable to me that the brain works as stated. Possibly, but I still need to read the librarys documentation carefully, where I plan my code anyways... I have seen so many "auto coders" write 100+ lines of extra code because they missed reading the manual carefully and doing it correctly/efficiently... If lines of code is your metric, that is great, if not, not...

kstenerud 6y ago

I never used autocomplete until my fourth programming language. By that point, trying to write anything was an exercise in frustration as I constantly mixed keywords, namespaces and functions from the other languages. Nowadays, I just leave autocomplete on for minimal flow break no matter what language I'm using at the moment. I don't want language-specific names and structures interrupting the flow of models and ideas from my head.

snarfy 6y ago

OP's position doesn't work very well the more you generalize. I had OP's philosophy when all I was doing was low level C code. It doesn't work very well when you are switching between yaml, python, c++, c#, typescript all with different libraries, coding standards, and naming conventions. By the time you no longer need the reference to remember, the reference changes.

svennek 6y ago
For me, it works with 5+ languages I write (production) code in at least every month... I don't know how it is for others. Also, I really try to minimize complexity and not ending up in the javascript npm dependency spaghetti.. Good code is simple and obvious....

svennek 6y ago

> I still think aurocomplete might be faster for libraries you haven't used much before, but it doesn't sound at all unbelievable to me that the brain works as stated. Possibly, but I still need to read the librarys documentation carefully, where I plan my code anyways... I have seen so many "auto coders" write 100+ lines of extra code because they missed reading the manual carefully and doing it correctly/efficiently... If lines of code is your metric, that is great, if not, not...