From IDE to life OS: what this trend really is
Developer tool repurposing is the growing habit of using professional code editors and IDEs for non-coding tasks like note-taking, journaling, and personal organization, turning a single technical workspace into a central hub for both work and life. VS Code is no longer treated as a narrow coding utility; it has become an ecosystem that many developers treat as an operating system in its own right. This shift matters because the tool where you spend most of your day shapes how you think. If your "home base" supports notes, tasks, and reflection alongside code, context switching drops and your workflow becomes more continuous. The trade-off is clear: less polish than consumer productivity apps, but far more control over how everything fits together.
VS Code as a notes app: from sidecar to main workspace
VS Code’s flexibility makes it a surprisingly strong VS Code notes app. By pairing its built-in file management with Markdown and a few extensions, one writer built a future-proof, local-first personal knowledge management system inside VS Code. Setting it up was simple: a dedicated notes folder, subfolders for daily notes and projects, and ordinary Markdown files that stay portable and non-proprietary. Markdown All in One improved day-to-day writing, while Foam—an open-source, local-first PKM extension for VS Code—added wiki-style links, backlinks, daily notes, and a knowledge graph. Once configured, using VS Code felt “not very different from using just another notes app.” The gains are obvious: a single editor handles code, research, and writing, and global search spans everything. The cost: there is no polished mobile app, rich-text canvas, or effortless web-clipping system included by default.
Open-source journaling shows what specialized tools still do better
If VS Code proves you can consolidate tools, open source journaling apps show why specialization still matters. StoryPad is an open-source, local-first journaling app for Android and iOS, designed specifically for daily reflections rather than general note-taking. The app keeps everything offline and local, with no account, ads, or dependency on an internet connection, which makes the journal feel private and self-contained. A timeline view turns scattered entries into a diary-like stream, encouraging users to scroll day by day and revisit past thoughts instead of burying them inside a generic notes pile. StoryPad supports Markdown for headings, lists, and checklists, and many advanced features—like customization, Markdown export to Notion or Obsidian, templates, and backgrounds—sit behind a paid tier. The limitations are real: it is mobile-only, and the local-first design means there is no seamless sync across devices. The implicit lesson: focus and constraints can strengthen a habit in ways a general-purpose editor rarely does.
Consolidation, familiarity, and the new shape of knowledge work
The most interesting pattern here is productivity tool consolidation. One author still uses Google Keep for quick ideas, reminders, shopping lists, and random snippets but relies on StoryPad when they want a dedicated space where personal thoughts do not get buried between everything else. Another keeps VS Code open as a notes workspace and reports that using it as a note-taking app for days left little to complain about. For developers, this is less about novelty and more about familiarity: the editor they already live in becomes the default place to capture anything. It is “especially useful for people who spend a lot of time in a code editor and don’t want to switch between tools whenever they need to take notes while working.” VS Code remains one of the best code editors largely because of its extensions. Those same extensions now enable life-logging, PKM, and even agentic automation on top of everyday coding.
So, should you turn your editor into your second brain?
This trend is not a universal prescription; it is a reflection of how knowledge work is changing. If you already live in VS Code, using it as a VS Code notes app can cut friction and give you a local-first PKM system tailored to your workflow, even if VS Code might not be a notes app replacement for everyone. If journaling is your priority, a focused open source journaling tool like StoryPad may serve you better than another catch‑all notes app. The real decision is philosophical: do you want one flexible environment that does many things reasonably well, or a constellation of specialized apps that each guard their own corner of your life? My view: developers should start from the tools they already know, experiment with developer tool repurposing, and then layer on dedicated apps only where habits are fragile or context is deeply personal.
