In light of that, I decided to search for a better way of editing files saved on a VM instance by connecting it to an existing IDE, to make tracking code changes easier, and to make debugging much more intuitive. All of this makes the process of fixing the bug a lot more complicated than it needs to be. The problem they face is that they are not as visually stimulating as an IDE, making you feel like you are coding in the simplest Text Editor, while in the case of Vim, it also has a very steep learning curve. Now those are great tools, especially Vim, which can automate your CI (read: Continuous Integration). That all seems pretty simple until you remember that initially, the only editors at your disposal when fixing these bugs are editors like GNU nano or the more popular Vim. After that, they get positioned in a terminal where they can then navigate to the required script where they believe the bug can be found, edit the script, and hopefully fix the issue. In the case of GCP, in order to make changes to the code, the engineer has to initially connect to the VM instance through SSH. Sometimes the application run on the VM instance experiences a behavior that cannot be easily explained and requires some additional debugging to understand, and fix the issue. More often than not, the code that gets placed in one of these VM instances requires some additional editing. Considering that they are very powerful tools engineers can use, they have become an essential part of web services that cloud providers such as GCP, Azure, and AWS, nowadays offer.

A virtual machine, or a VM, is a virtualized instance of a computer that can perform almost all of the same functions as a computer, including running applications and operating systems.

Visual studio code ssh terminal