4 ms·

At a former company, our newly appointed CTO staunchly advocated for the use of IntelliJ, including Webstorm and Pycharm. Coming from a predominantly Java envir

At a former company, our newly appointed CTO staunchly advocated for the use of IntelliJ, including Webstorm and Pycharm. Coming from a predominantly Java environment, this preference was understandable. However, our team was largely composed of Emacs or Vim users. This sparked a passionate debate, culminating in a disheartened CTO and an aggrieved development team that stubbornly stuck to their favored tools. Two key takeaways from this experience are: a) Avoid trying to impose your preferences onto your team, and b) don't attempt to strip away someone's preferred editor, especially if they are productive with it. A bit of humor added, these lessons highlight the importance of respecting individual tool choices in a team environment. :)

EdwardDiego 3y ago
I've always been an advocate of people using the tools that work best for them. But sometimes, there's better tools out there than $EDITOR, especially when working in large codebases. Like a recent PR where 4 out of 5 usages of a renamed variable also got renamed, but the last one didn't, and was in an area not covered by tests and it made it to main. (And yep, how it made it past review is a question I'll be asking...) The dev had switched from VS Code to Neovim recently and I'm reasonably certain that's related. I'm very comfortable riding motorcycles, but for taking my kids to school, I tend to use a car. Horses for courses.
- codethief 3y ago
  > (And yep, how it made it past review is a question I'll be asking...) Given that refactoring support in VSCode is not exactly great, either, and that even Jetbrains products have countless bugs in their "Rename" feature, I'd rather ask: How did the change make it past your merge request pipelines?
  - EdwardDiego 3y ago
    > an area not covered by tests Also, Django magic makes it very hard for tooling to actually know if something exists or not.
- WirelessGigabit 3y ago
  Check out the parent of the PR, rename in VS Code and see if it catches it.

EdwardDiego 3y ago

I've always been an advocate of people using the tools that work best for them. But sometimes, there's better tools out there than $EDITOR, especially when working in large codebases. Like a recent PR where 4 out of 5 usages of a renamed variable also got renamed, but the last one didn't, and was in an area not covered by tests and it made it to main. (And yep, how it made it past review is a question I'll be asking...) The dev had switched from VS Code to Neovim recently and I'm reasonably certain that's related. I'm very comfortable riding motorcycles, but for taking my kids to school, I tend to use a car. Horses for courses.

codethief 3y ago
> (And yep, how it made it past review is a question I'll be asking...) Given that refactoring support in VSCode is not exactly great, either, and that even Jetbrains products have countless bugs in their "Rename" feature, I'd rather ask: How did the change make it past your merge request pipelines?
- EdwardDiego 3y ago
  > an area not covered by tests Also, Django magic makes it very hard for tooling to actually know if something exists or not.
WirelessGigabit 3y ago
Check out the parent of the PR, rename in VS Code and see if it catches it.