The importance of knowing multiple IDEs for one programming language.

I have recently understood a new facet of coding and IDEs in particular. It is not just about the language you code in. Grasping the concepts of coding needs to be complimented with a solid experience of good IDEs. It is useful to learn to use multiple IDEs for a particular language.

When a starting developer tackles a new programming language, the general tendency is to use either the most common IDE (usually a feature-rich application but might be difficult to get started with) or the most basic IDE (usually devoid of advanced features but easy to get to grips with). Many times, starting developers 'zone-in' on the same IDE that they learn a new language on because overtime that IDE starts to feel familiar. This creates an inertia in the mind to switch over to a new IDE; something which they might need to do if the company they eventually get to work with, uses a different IDE for their internal development activity.

One of the most important things I learned during my internship at Delphi Automotive Systems is that when it comes to enterprise-level programming, the discipline of writing code is equally as important as the code itself. One needs to be open to try out new IDEs as different IDEs provide certain advantages or features over others. Also, most projects incorporate multiple languages and therefore multiple IDEs.

I think every developer should try out various IDEs for the same language. Those developers who are well-versed with the advanced IDEs should spend some time with the basic IDEs and vice versa. Such experience helps broaden your skill-set and creativity. If you're a seasoned developer and/or cannot use new IDEs at work, perhaps you can try a new IDE for the next personal project you pursue.

The ability to work in a varying coding environment will help one stay 'fluid' and maintain confidence when presented with a new challenge.

I emphasize as a side-note that this experimentation should be done once you're having a good grip on at least one IDE and the language you are using, in order to avoid confusion.