If you’re already working in Software and is already using an integrated development environment – IDE, you probably know someone who has been programming in a Notepad. Or now you are wondering why someone would do this… On the other hand, if you are starting in dev, you may be asking why on earth you should open a program full of little screens and divisions to write in one corner of the screen. You can’t even understand what’s written… Where’s the italics? The bold? How do you justify the text?
For these reasons and others, let’s talk about one of the system developer’s main tools: the IDE.
Definition
An IDE, or Integrated Development Environment, is a program that brings together tools that make programming easier. From formatting, Syntax Highlighting, to compilers, servers and integration with code versioning.
The most famous are:
- Java: Eclipse, Netbeans, IntelliJ;
- C#: Visual Studio;
- Anything Apple related: XCode;
- Javascript: Visual Studio Code;
Can you create your code in Notepad/VIM/Sheet of A4 paper and a pen? You can, but how quickly would you like to have your code written, validated (in the case of compiled languages), and running? Usually as quickly as possible, right?
The IDE can be seen as a fundamental tool for speeding up the process of typing and executing your code, as well as being the right place to create it and put it into production. More than that, remember that each language will have a more suitable environment, and quick shortcuts when written in the right program.
I don’t see any reason not to use it, not least because it’s very difficult to learn new languages or work without using them. It’s nice to know how to use editors without a graphical interface to be able to operate servers and so on, but for coding at development time (before deliveries and so on) an IDE is ideal.
Using an IDE: Advantages
I believe that when compared to a notepad, the advantages are: all.
- you get support for knowing which commands are available;
- you often have quick access to the documentation of a language/framework;
- syntax highlighting, colouring the syntax of the language used to make it easier to identify commands, variables, functions or methods;
- you get help with refactoring, etc;
- AI suggestions and autocompletion,
- and many others;
Using an IDE: Disadvantages
As with everything in computing: the more functionalities available, the more computer resources will be used. I don’t know if there’s a lighter IDE than a simple text editor (Notepad, Microsoft Word – but let’s not go that way), but I do believe it’s a valid trade-off (when it comes to functionalities vs. computer resources).
Conclusion
It’s always worth testing the IDEs that support the language/framework you’re using. Look for what’s available and test it out. Sometimes you’ll find complementary facilities and difficulties in different programs and one may be more to your liking than the other, yet you will only discover trying them.
Let me know in the comments or on Instagram which IDE is your favourite and which language you use.
Cheers and see you next time!
Leave a Reply