4 ms·

Question I have for everyone who doesn't use an IDE What is your workflow? I find the following to be true, in that one of 3 things happens inevitably: 1. The

Question I have for everyone who doesn't use an IDE What is your workflow? I find the following to be true, in that one of 3 things happens inevitably: 1. The Text Editor becomes the IDE, (e.g., with VSCode, if you just live in plain HTML, CSS/SCSS/LESS and JSX/TSX/JS/TS all day, its actually pretty great, lots of well maintained extensions and Microsoft really put their energy into capturing into this market with VS Code I think. If you have more than ~10 extensions installed, I'd argue you got an IDE (not including themes or colorizers)) 2. They have extensively curated vim or emacs setups that were built over time to add IDE-like features, in some cases I'd argue they become IDEs themselves via deep customization 3. They move to an IDE So my question is if none of the 3 are true, whats your workflow like? For context of my own workflow, it slowly over time is all around my IDE (JetBrains user, hardcore. You'll pry it from my cold dead hands). With the exception of running scripts (sometimes, like builds) and using git (git CLI is the best git interface IMO) I have moved it 100% into my IDE, and I'm so much faster at things, including picking up new languages When I started, I used VS Code heavily professionally, and vim before that, and relied on the CLI for anything outside of editing the code (basically, I think I had some auto formatting setup too), but I hit a wall at some point where I never turned back and went full into JetBrains to this day

deleted 6y ago
[deleted]
kccqzy 6y ago
I'm exactly what you describe at the end: a simple Emacs editor (with Evil) and CLI for almost anything else. Building and running code? They all happen in the terminal. Version control? I tried Magit, didn't like it, and went back to git CLI in a terminal. Auto formatter? Likewise in the CLI; in fact I have shell aliases that automatically run them when I commit. I haven't really hit a wall, and I personally think I'm just as productive, if not more, than IDE-using colleagues.
mixmastamyk 6y ago
Geany plus Makefile with automated functions. Build keys can be assigned to avoid Window switching. What walls were you hitting? Disclaimer, I have used Pycharm on a really big work project but most of the time, don't.
- no_wizard 6y ago
  Admittedly a lot of it is around things like built in documentation, viewing source code from inside modules (I’m a frontend software engineer so inside node_modules for instance) and the ability to simply let the IDE handle certain things with refactoring components or generating boilerplate. I found I repeated myself less and improved my productivity this way
  - mixmastamyk 6y ago
    Yep, I set up aliases and scripts for similar needs.
dmitshur 6y ago
I use a simple code editor with as few extensions as possible, and a terminal. My goal is to keep my setup as simple as possible so that I’m able to switch easily, but I’m not really looking for more features or functionality.
ben-schaaf 6y ago
I run a pretty much stock configuration of Sublime Text alongside gnome terminal. I have no issues navigating projects as large as gecko/WebKit/Linux and getting spun up on a new language is really fast: Open the project, maybe install syntax highlighting if needed and you're good to go - as opposed to finding/installing an IDE. My last Job had a large Java codebase and all my colleagues used Java based IDEs. I didn't see any performance disparity. I more than once saw a colleague take 5+ minutes making the same edit on a large number of lines because they hadn't learnt how to actually efficiently edit code in their IDE. The way I see it, you need to keep the codebases you're working on in your head anyway (the parts you're working with anyway) to actually be productive. You do this by reading and understanding the source code on the screen. Until an IDE can provide a tailored human interpretation of the code it's analysing rather than some narrow static analysis I just don't see the point.
- pier25 6y ago
  Same. I use Sublime with very few extensions. I have my own extensions for JS/CSS snippets and my custom color scheme, but that's it. I've used VSCode and Atom for a couple of years but they feel so bloated once you have multiple projects open at the same time. It's probably because I'm getting older, but I also find the UI quite annoying and distracting.
luord 6y ago
My answer is in this excellent series I read a while ago: https://sanctum.geek.nz/arabesque/series/unix-as-ide/ https://sanctum.geek.nz/arabesque/series/unix-as-ide/ Which, admittedly, is essentially the same as the other answers you got, but that's how I've been working for three years, since I decided to use vim exclusively. At the start, I was really tempted to install plugins, but ultimately I decided not to. Both to practice with the terminal (which has been immeasurably beneficial) and to make it as easy as possible to switch computers at the drop of a hat without losing productivity: just install vim and I'm good to go (and often not even that is required since vim comes preinstalled often enough).
Grue3 6y ago
For Python work I use a pretty much out-of-the-box Emacs, with "magit" being the only plugin of note installed. And I also used "web-mode" when I was doing webdev. magit is the best Git interface ever, and a built-in Emacs feature called TRAMP allows for remote editing. I'm running ipython in a separate terminal. I don't really understand why you'd need something more than a text editor to edit Python code. Now for Common Lisp I use SLIME, which I guess does count as IDE, seeing as it's much more powerful than most IDEs.

deleted 6y ago

[deleted]

kccqzy 6y ago

I'm exactly what you describe at the end: a simple Emacs editor (with Evil) and CLI for almost anything else. Building and running code? They all happen in the terminal. Version control? I tried Magit, didn't like it, and went back to git CLI in a terminal. Auto formatter? Likewise in the CLI; in fact I have shell aliases that automatically run them when I commit. I haven't really hit a wall, and I personally think I'm just as productive, if not more, than IDE-using colleagues.

mixmastamyk 6y ago

Geany plus Makefile with automated functions. Build keys can be assigned to avoid Window switching. What walls were you hitting? Disclaimer, I have used Pycharm on a really big work project but most of the time, don't.

no_wizard 6y ago
Admittedly a lot of it is around things like built in documentation, viewing source code from inside modules (I’m a frontend software engineer so inside node_modules for instance) and the ability to simply let the IDE handle certain things with refactoring components or generating boilerplate. I found I repeated myself less and improved my productivity this way
- mixmastamyk 6y ago
  Yep, I set up aliases and scripts for similar needs.

dmitshur 6y ago

I use a simple code editor with as few extensions as possible, and a terminal. My goal is to keep my setup as simple as possible so that I’m able to switch easily, but I’m not really looking for more features or functionality.

ben-schaaf 6y ago

I run a pretty much stock configuration of Sublime Text alongside gnome terminal. I have no issues navigating projects as large as gecko/WebKit/Linux and getting spun up on a new language is really fast: Open the project, maybe install syntax highlighting if needed and you're good to go - as opposed to finding/installing an IDE. My last Job had a large Java codebase and all my colleagues used Java based IDEs. I didn't see any performance disparity. I more than once saw a colleague take 5+ minutes making the same edit on a large number of lines because they hadn't learnt how to actually efficiently edit code in their IDE. The way I see it, you need to keep the codebases you're working on in your head anyway (the parts you're working with anyway) to actually be productive. You do this by reading and understanding the source code on the screen. Until an IDE can provide a tailored human interpretation of the code it's analysing rather than some narrow static analysis I just don't see the point.

pier25 6y ago
Same. I use Sublime with very few extensions. I have my own extensions for JS/CSS snippets and my custom color scheme, but that's it. I've used VSCode and Atom for a couple of years but they feel so bloated once you have multiple projects open at the same time. It's probably because I'm getting older, but I also find the UI quite annoying and distracting.

luord 6y ago

My answer is in this excellent series I read a while ago: https://sanctum.geek.nz/arabesque/series/unix-as-ide/ https://sanctum.geek.nz/arabesque/series/unix-as-ide/ Which, admittedly, is essentially the same as the other answers you got, but that's how I've been working for three years, since I decided to use vim exclusively. At the start, I was really tempted to install plugins, but ultimately I decided not to. Both to practice with the terminal (which has been immeasurably beneficial) and to make it as easy as possible to switch computers at the drop of a hat without losing productivity: just install vim and I'm good to go (and often not even that is required since vim comes preinstalled often enough).

Grue3 6y ago

For Python work I use a pretty much out-of-the-box Emacs, with "magit" being the only plugin of note installed. And I also used "web-mode" when I was doing webdev. magit is the best Git interface ever, and a built-in Emacs feature called TRAMP allows for remote editing. I'm running ipython in a separate terminal. I don't really understand why you'd need something more than a text editor to edit Python code. Now for Common Lisp I use SLIME, which I guess does count as IDE, seeing as it's much more powerful than most IDEs.