Skip to content

2026

From PyCharm to VS Code

After five years of extensively using PyCharm Professional, I’ve encountered several persistent issues that ultimately led me to switch to VS Code. These include:

  1. Plugin Development and Maintenance: Challenges in developing and maintaining PyCharm plugins.
  2. Performance Issues: Slow operation and excessive resource consumption.
  3. Remote Development Limitations: Weak support for remote development workflows.
  4. AI Extension Bugs: Frequent bugs in AI-powered features.
  5. Critical Bugs: Increasingly severe issues requiring manual deletion of cache and library files to restore functionality.

Given these frustrations, I decided to transition to VS Code. This document outlines the steps I took during the migration from PyCharm to VS Code.

Elegant Env Vars for Jenkins Python

In my case, I use Jenkins to drive some Python scripts. We can set configuration in Jenkins via System Properties, Node Configuration or Build Parameters.

We can get the configurations through environment variables, and also pass stage outputs to other stages via environment variables.

Visualizing and retaining environment variables is crucial, So I want to manage environment variables in an elegant way.

I implemented a class EnvSettings extend from pydantic.BaseSettings to manage environment variables: