4 ms·
The thing I’m not a huge fan of with the IntelliJ model is that it’s super tooling-dependent. I would rather work with a set of loosely-coupled tools and autom
by skohan 5y ago
The thing I’m not a huge fan of with the IntelliJ model is that it’s super tooling-dependent. I would rather work with a set of loosely-coupled tools and automate my own workflows.
- jpgvm 5y agoTo be honest I used to be the same way. Used desktop linux (gentoo then arch), tiling wm (xmonad), 3k line vimrc with every plugin you could want, tons of scripts to automate gdb/valgrind/etc. Then something happened, I'm not sure what. Maybe I just got old but I no longer derived value from it being -my- setup. I just wanted whatever got the job done most efficiently. These days I'm ultra boring. I run macOS everywhere, I still use zsh and a fairly pimped shell, but minimal vimrc and IDEA has replaced the vast majority of my dev environment. It doesn't have any of the personality it once did and tbh that doesn't bother me in the slightest.
- skohan 5y agoYeah it’s not so much about being my setup, I think its more that I’ve gotten used to working this way and I don’t want to learn a whole big tool which might not do exactly what I want. With most of my projects, I have a couple of scripts to take care of the tasks relevant to that project. When I start something new, I just copy them over from a similar project and edit where needed. Super light weight, and basically will work until the end of time. For work sometimes I need to adopt someone’s highly tooled workflow, and then you have to get the editor license, find the right plugins, make sure you’re on the same version and so on. And sometimes you dust off an old project and something broke in this big magical dependency chain and you have to do surgery to figure out what it is.
- mleonhard 5y agoI had the same experience. One day I realized that I no longer enjoyed doing sysadmin work, especially on my own machines. I began to loathe complicated config files that require reading manuals to figure out how they work. Examples: SystemD, NixOS, Bazel, and BCL/GCL. Even worse are tools that silently ignore errors in config files. Examples: Gulp, ESLint, and nearly every other tool written in JavaScript. Now I use a single machine with macOS and leave nearly every setting at the default. I don't even use Brew. I prefer to use tools that come with their own installers and updaters. I think this change happened when I finally found work that difficult for me and took all of my energy. I had no energy left over to waste on sysadmin work. Also, my brain began to fill up with knowledge of systems programming, languages, and libraries. Recalling details of random config files takes more effort than before. I think my brain has a hierarchical memory system with four types of long-term memory: 0. Knowledge available instantly 1. Knowledge retrievable with 2-3 seconds of concentration 2. Knowledge that is unavailable upon request, but usually pops into mind 1-2 minutes later. 3. Knowledge that I can retrieve only with an associated memory or idea. When I was a teenager, my technical knowledge fit into my tier 0 memory. Then I earned a degree and worked some years and my knowledge grew to fill tiers 0 & 1 and some has been relegated to tiers 2 and 3. I take and keep many photos because I can use them years later to retrieve forgotten memories. Maybe I will start taking screenshots of my computer to use in a similar way.