Using Different IDEs in the same development team

I'm about to join a new (Java) development team and a thought came to mind - do they use Eclipse? I have been working with Eclipse for the past 6 years and don't see myself switching to another IDE if the team is using that IDE (e.g. IntelliJ).

Is it a problem to use different IDEs in the same development t开发者_如何学编程eam?

---

Yes. It's a problem.

As a 3-decade contractor -- having been to a new client (on average) every 6 months -- I have some advice.

Get over it.

Seriously. Whatever they're using is fine, really. Use it. Learn it.

Why?

A) You'll know more IDE's, be more valuable, and more skilled.

B) You can share knowledge more easily.

C) The point is not the tools. The point is the product.

---

It's not a problem technically. It's more a factor of time and using the same tools as your development team. You'll have to create a different set of configuration artifacts (like .project and .classpath) to check in and maintain. It could range from easy to hard, depending on how their project(s) are setup. You should also consider that it'll be harder to get support and give support inside your team.

---

I work at a company where we recommend using IntelliJ, but some people use Eclipse. It's not really a big issue to be honest. It depends on how the company structures the code.

Just as a sidenote: I used to use eclipse, but since I started using IntelliJ, I'm never going back. It's just so much nicer to work with. Once you get the hang of all the shortcuts, I can honestly say that intellij is better for me in terms of productivity. YYou can get used to it within a month.

---

Is it a problem to use different IDEs in the same development team?

It depends on the team, but the answer is often yes.

• If the team norm is to use Eclipse and you insist on using IntelliJ, you could get a reputation for being "difficult" ... especially if the team culture is not to innovate.

• You are likely to cop the blame if this causes issues / inconsistencies; e.g. it results in code style issues, different compilation warnings. Indeed, you may cop the blame for problems that are not caused by Eclipse versus IntelliJ issues ... when someone else says that they are. (Not fair, but life is like that.)

• On certain projects there can be issues with availability of plugins, and so on. By using Intellij, you could have problems right now, or you could restrict the ability of the project as a whole to use new tools. (I'm thinking of things like Eclipse EMF, ESC2Java and so on.)