Earlier quoted context omitted.
Putin has nothing to do with it, pretty sure he doesn’t even know who they are. JetBrains founders are Russians, but they registered the company in Prague as their goal was foreign markets from the beginning and it was much safer to do business there than in 90’s Russia. Most of their programmers and RnD were Russians, they had close ties with several top Russian Universities to hire students from there. But yes, in…
> But yes, in 2022 they were told by their Western customers that they have to leave if they want their products to be bought, and JB evacuated from Russia, relocated people and fired those, who refused to leave, blocked Russian customers and in some cases terminated their ongoing licenses, forced their employees to cut any cooperation with Russia (their head of Kotlin decided to quit the company due to this policy a…
My company has banned the use of Jetbrains IDEs internally
151–160 of 201 posts
Re: My company has banned the use of Jetbrains IDEs internally
#152Earlier quoted context omitted.
Maybe i just never gave the heavyweight ide tools a fair chance, but i always found them more distracting than helpful. Focus is king for me, and vim gives me that.
VSCode is not a heavyweight IDE by any means.
Re: My company has banned the use of Jetbrains IDEs internally
#153I've seen so many editors come and go, and yet I've been using Vim for the past 20 years and have never had a problem. As stupid as it sounds, if I could give one piece of advice to any entry level SWE, it would be to learn Vim or Emacs and just stick with it for your whole career.
I don't even know what to say to this other than that you are right that it does sound stupid and it is stupid. A software developer should not be afraid of learning software, learning new things is fundamental in our work. Comparing an IDE with basic editor like vi, really, that may have worked out for you since you started 20 years ago when that worked, but it should not be the advice today.
Re: My company has banned the use of Jetbrains IDEs internally
#154Earlier quoted context omitted.
I quit over principles about 9 months and 800 job applications ago. I'd advise not to do it unless you're sitting on a pile of cash.
I'm genuinely super curious because I hear this a lot, but the deepest I ever got was... 5 apps? Do you have some kind of like generic cover letter/resume you fire off 3 times a day? What is your process?
Re: My company has banned the use of Jetbrains IDEs internally
#155I've seen so many editors come and go, and yet I've been using Vim for the past 20 years and have never had a problem. As stupid as it sounds, if I could give one piece of advice to any entry level SWE, it would be to learn Vim or Emacs and just stick with it for your whole career.
How can you possibly be as productive as someone working in Visual Studio? I'm asking honestly - working without the solution explorer, being able to look at any immediate variable, instruction pointer dragging, and others seems like it would slow me down immensely.
I am also excited by the fact that the text editor configuration is programmable in a Turing-complete language, as opposed to pure JSON configurations that VS Code offers (correct me if I'm wrong, but settings are just a JSON file right?). It means that anything is possible.
In VSCode, my biggest complaint was that, for the Vim extension, the status bar was not configurable - I wanted to make the whole page change color when in "Normal" mode, versus "Insert" mode. Not possible in VSCode, but it's only a handful of lines of Lua in Vim.
Is that a huge productivity boost? No, but it makes me happy. Just as much as I want to be productive, I also want to be happy while programming
Re: My company has banned the use of Jetbrains IDEs internally
#156Earlier quoted context omitted.
Since I graduated, I've had people try to sell me on the following editors, which were going to be the future: BBEdit, TextMate, Sublime Text, Atom, Komodo Edit, NetBeans, and Eclipse. Each was going to kill Emacs. Somehow, I think I'll be using a version of Emacs until the day I can no longer type. Meanwhile, everyone else is wasting months getting up to speed on the latest and greatest thing every 8 years or so. Th…
>Meanwhile, everyone else is wasting months getting up to speed on the latest and greatest thing every 8 years or so. Yeah I used to think this way, because you're right: becoming proficient in emacs takes significant effort and time. But becoming proficient in VS code takes maybe 25 minutes. 25 minutes to change IDEs every 8 years or so doesn't seem like an onerous requirement to me. Emacs just has extremely poor de…
Re: My company has banned the use of Jetbrains IDEs internally
#157Earlier quoted context omitted.
>But becoming proficient in VS code takes maybe 25 minutes. Becoming proficient in kicking a ball takes 5 minutes. Becoming proficient in football takes slightly longer. Magit alone makes VS Code look like a child's finger painting.
>Magit alone makes VS Code look like a child's finger painting. Magit is indeed a great git client, but I don't see what that has to do with emacs having bad defaults and an out of box experience that could be charitably described as antique.
Re: My company has banned the use of Jetbrains IDEs internally
#158Earlier quoted context omitted.
I find this and the emacs sentiment really weird. I use vim daily for quick edits, but for any sizeable codebase, especially new/unfamiliar, IDE's are just better. It's like depriving yourself of a bunch of tools and helpers for no visible benefit.
Maybe i just never gave the heavyweight ide tools a fair chance, but i always found them more distracting than helpful. Focus is king for me, and vim gives me that.
Re: My company has banned the use of Jetbrains IDEs internally
#159I've seen so many editors come and go, and yet I've been using Vim for the past 20 years and have never had a problem. As stupid as it sounds, if I could give one piece of advice to any entry level SWE, it would be to learn Vim or Emacs and just stick with it for your whole career.
Vim is great but I think VSCode really is the one tool to rule them all going forward. It's extremely well designed, snappy, and I think does the correct thing of first treating everything as a text file and allowing plugins to provide semantic meaning. I never liked visual studio because it was too specific to writing software and using the GUI to do what I wanted. Editing msbuild files directly was a pain for examp…
Example from VSCode Terminal: $ echo hello | code -
Re: My company has banned the use of Jetbrains IDEs internally
#160Earlier quoted context omitted.
Care to elaborate what's wrong with find and grep?
It takes seconds or more to grep for a function, especially if it has a common name. It takes milliseconds to Go To Definition / Find Usages (either with an IDE or a LSP extension for any text editor).
I see your point though. I guess I just disagree with the premise that using an IDE will increase productivity.
The developer will always have to invest some effort into learning the tools, be it find and grep or an IDE.