Why I Switched from Sublime Text to Visual Studio Code

So then I gave it a go, and surprisingly.. I’m convinced that this will be my new go-to code editor replacing Sublime Text in just 3hours or more playing around with it.

Here’s why..

Okay. As I mentioned before, one of the reason why I chose Sublime previously is because it’s fast and light-weight. It’s a crucial aspect of a code editor for me personally.

But using VS Code on the other hand. It’s (still) feel fast. I noticed that Sublime Text is still faster on some areas, but I can barely notice the difference.

This is by far one of the best feature made for people nowadays, who were constantly interrupted by notification from our gadgets. We got enough distractions from phone, so a distraction-free mode while you’re working on your codes is a pretty neat feature to boost your productivity I bet.

Since I came from a non-technical background, somehow I tend to avoid using Terminal for all of my web development projects (yes, I survived building a web development company when I’m wearing my frontend developer hat with that mindset for years).

But since one of my new year’s resolution as a frontend developer is to become a full-fledged frontend developer, I guess I can’t run from it anymore (hello React, Vue.js, and friends).

So.. having a Terminal which directly pointed to your working folder is definitely a plus point for me now.

The issue with writing codes for years, is that you tend to be really good at “writing” it, or in this case “typing” might be a more suitable word. I’m not saying that it’s bad, it’s just.. inefficient.. to type the same things / structure over and over again.

Or in another case, when you can’t remember the exact code you’re trying to type, and you’re gonna spend the next minutes (or even hours) searching for that line of code on Google.

That’s where IntelliSense came to help. Intellisense will smartly predict what you’re going to type and give you suggestions based on the context. Not only that, it can even gave me useful quick info sometimes.

This is one feature that I found pretty handy. When working in a project with thousands of lines of codes, one thing I hate the most is when I have go back and forth navigating through those lines to check on something.

Using the peek feature, it allows me to navigate between references and make changes right there, without having to go to the real location of the code.

So that’s about it. My personal take on Visual Studio Code.

It got a lot more interesting features than those I mentioned above of course (e.g. snippets, debugging, built-in versioning control, etc.), but those five features I mentioned are subjectively my favorite.

So if you’re currently in the same position as mine previously, comfortable using Sublime Text and haven’t try Visual Studio Code yet, I’d suggest to give it a try. At least for a couple hours or a couple days, and then decide it for yourself if it increases your productivity. It certainly increased mine.

Everyone has their own style of working, but who knows my experience above would help you in any way.

P.S. Sublime Text, don’t worry, you still have special place in my heart.

🦈

Related posts:

This article will focus on moving the Laravel Auth views completely to VueJS with the exception of Login. We will keep the Laravel backend mostly the same, but will only serve the index file from…

Some of my life experiences. Inspiring to be an entrepreneur, moving to San Francisco, working at a fast growing startup, the YC network, and founding Middesk.

A king of Bollywood SRK has a keen interest in helping our India to make it clean. He proponent with posting tweets regarding the advantages of cleanliness and representing the ambassador of Hyundai…