VS Code is the best productivity app on my PC, and I barely use it for coding anymore

At a glance:

• VS Code evolves from a coding IDE to a daily productivity tool for notes, logs, and documentation.
• Its file-native approach avoids data lock-in, unlike Notion or Obsidian.
• Built-in terminal and extensions make it a versatile hub for text editing and command execution.

From code editor to productivity hub

When Korbin, a Linux system administrator, first downloaded Visual Studio Code, he intended it for coding. Over time, however, he found himself reaching for it daily—not for writing Python scripts or debugging JavaScript, but for opening log files, drafting articles, and jotting down notes. This shift mirrors a growing trend where users repurpose VS Code beyond its intended IDE role, leveraging its robust text editing capabilities for general productivity tasks. The appeal lies in VS Code's simplicity and power. Unlike specialized apps that impose workflows, VS Code acts as a blank canvas. Korbin stores his notes as Markdown files on his desktop and homelab documentation as plain text, and VS Code handles both without complaint. This flexibility has made it one of the most-used applications on his PC, proving that its value extends far beyond coding environments.

The file-native philosophy

A key differentiator for VS Code is its file-native approach. Services like Notion intertwine your workflow with their platform, risking data lock-in if the service disappears. Obsidian is better since it uses local files, but it still encourages a vault-based structure that can feel confining. VS Code, by contrast, simply opens a folder and lets you arrange files as you see fit, with no proprietary formats or migration hurdles. This philosophy resonates with users who prioritize data ownership. Korbin appreciates that his files remain just files—accessible in any editor, not trapped within an app's ecosystem. Whether it's docker-compose files, configs, or CSVs, VS Code provides syntax highlighting and formatting without demanding import rituals or long-term commitments. It's an interface that respects user autonomy, a rarity in today's productivity software landscape.

Extensions: supercharging versatility

The extension ecosystem transforms VS Code from a mere editor into a Swiss Army knife. Korbin has experimented with REST clients, database browsers, Markdown previewers, and diff tools—each performing on par with or better than standalone utilities. Having these tools integrated into a single window eliminates the need to switch contexts, streamlining workflows for tasks like API testing or document comparison. Extensions also cater to niche needs, allowing users to customize VS Code for specific domains. For instance, a developer might add Docker or Kubernetes extensions, while a writer could install grammar checkers or citation managers. This adaptability means VS Code can morph to fit almost any text-based task, reinforcing its status as a general-purpose tool rather than a coding-specific one.

Integrated terminal: a game changer

Perhaps the most transformative feature is VS Code's built-in terminal. Unlike other text editors that separate writing from execution, VS Code combines them in one pane. Korbin illustrates this with his homelab documentation: he keeps setup notes in one pane and runs commands in the terminal below, copying steps directly from his notes. This integration saves time and reduces errors compared to alt-tabbing between a text editor and a command prompt. The terminal supports various shells and environments, including Windows Subsystem for Linux (WSL), making it invaluable for sysadmins and developers alike. It turns VS Code into an interactive workspace where documentation and action coexist, a capability that apps like Notepad++ or Obsidian cannot match. This seamless blend of editing and command-line access is a cornerstone of VS Code's productivity appeal.

Why VS Code beats the alternatives

While apps like Obsidian and Notion fill productivity niches, Korbin finds them limiting. Obsidian uses local Markdown files and has a strong plugin ecosystem, but it still tries to be the central repository for all thoughts. Notion goes further with its proprietary service, locking users into a database-driven model. VS Code, however, is more versatile—it handles any text file without imposing structure, making it a freer option for diverse workflows. Obsidian and Notion excel in specific areas: Obsidian for linked notes, Notion for databases. But for users who work with varied file types—logs, configs, CSVs—VS Code's agnosticism is a strength. It doesn't force a knowledge management system or a project tracker; it just edits text, with extensions adding functionality as needed. This simplicity and openness make VS Code the preferred choice for those who value flexibility over specialized features.

Conclusion: rethinking the tool

Visual Studio Code's journey from coding IDE to productivity staple highlights a broader lesson: tools should adapt to users, not vice versa. By shedding its "code editor" label and embracing a general-purpose text editing role, VS Code has won over users like Korbin who need a reliable, extensible interface for their files. Its built-in terminal, extension support, and file-native design combine to create a hub that transcends traditional categories. For anyone skeptical of VS Code due to its name, Korbin's experience suggests giving it a try. Whether you're a developer, sysadmin, writer, or just someone who handles lots of text files, VS Code might become your go-to app—not for writing code, but for getting work done. In an era of app overload, its versatility is a refreshing change.