TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Is standardizing on IDE beneficial for your team?

2 点作者 shoarek将近 5 年前

3 条评论

bkanber将近 5 年前
As a manager, I&#x27;ve seen this play out both ways. These days, great IDEs (and IDE-ish-s) are easier to find (points at VSCode). But just a few years ago the landscape was a bit bleaker, and I successfully introduced Jetbrains&#x2F;PhpStorm (and also vim keybindings ;) to many team members who otherwise would not have ventured to update their workflow. They all loved it!<p>More recently, I&#x27;ve shown devs PhpStorm and, after trying it, they want to stick with VSCode. I&#x27;m fine with that, as long as the PRs come in clean and they&#x27;re able to maintain their development environments otherwise.
coder4life将近 5 年前
Last time this was mandated for me it was Eclipse. Slow as molasses and gets in the way (way back in 2008 that is). IDEs should keep up with your typing, not just eventually catch up to it, IN ALL CASES! A slow editor kills performance for me
luxurytent将近 5 年前
Agree with the conclusion.<p>What is output for eventual review needs to be standardized and consistent. If a human has to nag about formatting or similar nuance, we’re doing something wrong.<p>IDEs don’t define the output, but code formatters and linters do. That must be standardized.