Moving to Visual Studio Code (It’s Better than PyCharm)

The first time I focused to learn programming (about two months ago), I used PyCharm as my IDE (Integrated Development Environment).

There is no reason for that. I used PyCharm simply because of the tutorial I watched at that time use PyCharm. Therefore I do that.

But after using PyCharm for a while, it seems to me that the program is quite heavy and the UI is not really good.

I tried to install the Visual Studio Code (VSCode)… The UI is better and I like it. But because I don’t know how to use VSCode (how stupid I am)—as I already familiar with PyCharm, I was going back to PyCharm.

I can’t forget the feel of clean UI in VSCode, therefore I tweaked my PyCharm to look like VSCode.

The look of my PyCharm after tweaked (It’s better than the original version)

Last week, finally I decided to try VSCode (seriously).

And it turns out that it is really better. The UI, the feel, and other things are all better. It is also not that complicated (as I think before).

The look of VSCode

After few days using VSCode, I think I will never go back to PyCharm.


Here is the not about one important thing when I moved from PyCharm to VSCode:

Working with Virtual Environment

In PyCharm, working with Virtual Environment (venv) is very simple. There’s an option to do that when starting a new project.

But in VSCode, it should be done manually.

The command to start venv:

python -m venv .venv

The command to activate the venv:

.venv/Scripts/activate

If the activate command generates the message “Activate.ps1 is not digitally signed… here is the thing to do:

Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope LocalMachine

By Fajrul

Amateur physicist and science writer

Leave a comment

Your email address will not be published. Required fields are marked *