Are you more independent for it? Sure, I guess. But I'd rather be efficient then get brownie points
Benefits of Not Using an IDE
211–220 of 389 posts
Re: Benefits of Not Using an IDE
#212I guess it depends on your definition of an IDE, and where you're most comfortable/productive. I see a lot of posts about autocomplete, refactoring, linting, tooltips, tests-by-cursor/file, snippets. Thanks to a very friendly plugin community, you can get all of these in vim, emacs etc. I like vim, and it has nothing to do with hubris. For me it's mostly about: 1. proximity to the terminal: I find cli tools very usef…
> 0% adjustment when working over SSH: tabs, splits, etc. both in my editor and terminal are identical in an SSH session. No discomfort. Mostly useful at home.
Aren't these two benefits mutually exclusive? If you're got a very personalised vim setup, then vim on your workstation is going to be potentially dramatically different to vim when sshed into a remote machine
Re: Benefits of Not Using an IDE
#213Well, I get linters (errors are highlighted even before the file is saved), jump to function definition and a lot more in Sublime Text. I mean, I don't use an IDE, but at the same time, reading the comments, I don't miss much of what it offers.
Re: Benefits of Not Using an IDE
#214Listen, long story short: just say no to nonsense like this. Given the choice of a) tooling, or b) no tooling, you’re not being smart, cool or clever by choosing b. Obviously, what tools you pick are important and heavy IDEs like IntelliJ are a trade off between speed and functionality, and yeah, more nimble tools do exist, and it’s definitely worth trying different development tools to see what makes you most produc…
The best developers I've found are the ones who know how to work without an IDE, even if their preference is to use one. Contrastingly, the worst, slowest developers I've worked with rely on their IDE without understanding what it's doing for them, and are helpless in new/unsupported situations. They also, 100% of the time, screw up their git repositories on a regular basis, and need someone who knows what they're do…
Re: Benefits of Not Using an IDE
#215Earlier quoted context omitted.
He's referring to Visual Studio. https://visualstudio.microsoft.com/
I find Visual Studio auto complete 100x better then VS Code auto complete.
(it is 'than', not 'then')
Re: Benefits of Not Using an IDE
#216Listen, long story short: just say no to nonsense like this. Given the choice of a) tooling, or b) no tooling, you’re not being smart, cool or clever by choosing b. Obviously, what tools you pick are important and heavy IDEs like IntelliJ are a trade off between speed and functionality, and yeah, more nimble tools do exist, and it’s definitely worth trying different development tools to see what makes you most produc…
The best developers I've found are the ones who know how to work without an IDE, even if their preference is to use one. Contrastingly, the worst, slowest developers I've worked with rely on their IDE without understanding what it's doing for them, and are helpless in new/unsupported situations. They also, 100% of the time, screw up their git repositories on a regular basis, and need someone who knows what they're do…
People take pride in being less productive and making things harder than they need to be.
Re: Benefits of Not Using an IDE
#217My eye twitched when I read this. My company recently switched to a new build system and for whatever reason this required (I guess??) a change to the src/main/java... structure. The commit history going back over a decade, gone. It's not great.
Re: Benefits of Not Using an IDE
#218Re: Benefits of Not Using an IDE
#219Well, I get linters (errors are highlighted even before the file is saved), jump to function definition and a lot more in Sublime Text. I mean, I don't use an IDE, but at the same time, reading the comments, I don't miss much of what it offers.
Sure but doesn't that just mean sublime is a pretty good IDE?
Re: Benefits of Not Using an IDE
#220Earlier quoted context omitted.
The best developers I've found are the ones who know how to work without an IDE, even if their preference is to use one. Contrastingly, the worst, slowest developers I've worked with rely on their IDE without understanding what it's doing for them, and are helpless in new/unsupported situations. They also, 100% of the time, screw up their git repositories on a regular basis, and need someone who knows what they're do…
That sounds more like a problem with git than a problem with the IDE. Why does git allow you to screw up your repository?