4 ms·

This. I find it's even more valuable with the explosion of 3rd-party libraries and packages--I'm constantly interfacing with code I didn't write, and autocomple

This. I find it's even more valuable with the explosion of 3rd-party libraries and packages--I'm constantly interfacing with code I didn't write, and autocomplete is _way_ faster than context switching to look at the docs/source of a library.

jonhohle 7y ago
Yeah, really! Who would want to read the docs of a library!?
- scarface74 7y ago
  So let me introduce you to Boto3.... https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/index.html https://boto3.amazonaws.com/v1/documentation/api/latest/refe...
- bradstewart 7y ago
  I always read the docs first. And then usually skim the source code (when available). But that doesn't mean I've memorized every method name and signature.
- omaranto 7y ago
  I think you meant to ask who would want to memorize the docs and never ever need confirmation they are remembering correctly?
aratakareigen 7y ago
Interesting, but why not just have the autocomplete as a pane on the side so that you can focus, in the 99% case where you do have a good grasp of your dependencies?
- bradstewart 7y ago
  That would certainly be a viable middle ground, but I simply don't find the in-editor popup to be distracting. I find a good many things distracting while working, but I actually like the autocomplete popups.
  - cdo256 7y ago
    I don't think the main problem is that they're distracting, in the drawing attention away from what you're writing sense. I think the main problem is that, for an unfamiliar editor, the autocomplete takes an unknown subset of keystrokes, meaning that common things like inserting a newline or navigating vertically can interrupt your train of thought. Once you get familiar with a particular editor then these problems become less acute. What remains is the obscuring of other lines of code which can be fixed by making the autocomplete box only appear when you press tab.

jonhohle 7y ago

Yeah, really! Who would want to read the docs of a library!?

scarface74 7y ago
So let me introduce you to Boto3.... https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/index.html https://boto3.amazonaws.com/v1/documentation/api/latest/refe...
bradstewart 7y ago
I always read the docs first. And then usually skim the source code (when available). But that doesn't mean I've memorized every method name and signature.
omaranto 7y ago
I think you meant to ask who would want to memorize the docs and never ever need confirmation they are remembering correctly?

aratakareigen 7y ago

Interesting, but why not just have the autocomplete as a pane on the side so that you can focus, in the 99% case where you do have a good grasp of your dependencies?

bradstewart 7y ago
That would certainly be a viable middle ground, but I simply don't find the in-editor popup to be distracting. I find a good many things distracting while working, but I actually like the autocomplete popups.
- cdo256 7y ago
  I don't think the main problem is that they're distracting, in the drawing attention away from what you're writing sense. I think the main problem is that, for an unfamiliar editor, the autocomplete takes an unknown subset of keystrokes, meaning that common things like inserting a newline or navigating vertically can interrupt your train of thought. Once you get familiar with a particular editor then these problems become less acute. What remains is the obscuring of other lines of code which can be fixed by making the autocomplete box only appear when you press tab.