A working developer's honest review, not a sponsored listicle. 34 extensions down to 18, startup time from 4.2s to 1.1s, here's exactly what changed.
I clocked my VS Code startup time: 4.2 seconds. That's with 34 extensions installed, 11 of which I hadn't touched in six months.
So I ran a full audit. Removed, replaced, reconfigured. Startup time after: 1.1 seconds.
Here's exactly what I changed and why.
Step 1 — The audit process
Open the command palette (Cmd/Ctrl + Shift + P) and type:
I tried more than forty VS Code extensions while working on full stack projects this year. Most of...
Before we start — a warning. This isn't one of those lists where I throw 25 extension logos at you...
After the massive response to my first post on VS Code extensions, I had to make a Part 2! Many of...
I Built a VS Code Extension to Track My Coding Time — And Kept Your Data 100% Local Tags:...
As a MERN Stack developer, I spend most of my day inside Visual Studio Code. Over time, I realized...
For years, VS Code was the obvious default. It was fast, extensible, familiar, and good enough for...
