3 ms·
I think one difference you and I have is, I've pretty much ditched the idea of autocomplete being a useful thing so I don't depend on it with any editor. This i
by nickjj 8y ago
I think one difference you and I have is, I've pretty much ditched the idea of autocomplete being a useful thing so I don't depend on it with any editor. This is coming at it from a Python, Ruby, Elixir point of view.
This is mainly because of 2 things:
1. 99% of the apps I develop are Dockerized and there's no editor that flawlessly handles that
2. I've tried PyCharm, RubyMine, etc. and the autocomplete never really saves me that much time. In my mind "pretty good autocomplete" is worse than no autocomplete. Pretty good autocomplete usually slows you down overall because it's good, but not good enough. I still always find myself referencing documentation which means autocomplete didn't really do anything except maybe save typing a few characters.
- konart 8y agoI've been coding in Python and Ruby most of the time and now it's Ruby with Go. And while I agree that autocomplete is less usefull with Ruby due to it's nature - it saves a ton of time while developing in Go. And sometimes you simply don't have any documentation to reference. So it's 'go to definition' and autocomplete all the way through. 1. What's the problem with it being Dockerized? I have my current project Dockerized too. JI just have :volumes in my docker-compose for development. If source code access is what we are talkig about. 2. see the above