4 ms·
> Our dev team made the unanimous call to move require all developers to use Jetbrains IDEs Wow, it'd be time to look for a new job. I think having a blessed
by ParetoOptimal 4y ago
> Our dev team made the unanimous call to move require all developers to use Jetbrains IDEs
Wow, it'd be time to look for a new job.
I think having a blessed option and understanding of "use what you want but don't let it affect deliverables" is best.
- cameronh90 4y agoWhile I've never worked anywhere that enforced the IDE, I can see the appeal. Problems like linting and formatting working differently for different developers because they're using different tools, not updating settings correctly because their IDE uses a different settings file. Junior developers struggling to find people to help them because everyone's using their own toolchain. It's not all just about deliverables.
- indymike 4y ago>Wow, it'd be time to look for a new job. Everyone on the team agreed. If one person had said no, we would not have made the jump. > I think having a blessed option and understanding of "use what you want but don't let it affect deliverables" is best. That's kind of how it worked out for us. We didn't ban emacs or vs code, we just all agreed we'd go Jet Brains first and mostly... and for the more senior of us (me especially), go out of the comfort zone and learn the new tool.