Sitemap
CodeToDeploy

Tech Insights | Careers | Jobs

Member-only story

The VS Code Extensions I Open Every Single Day

--

Seven tools that survived a ruthless cleanup, and the ones I deleted without regret.

Press enter or click to view image in full size
C# code in VS Code with a GitLens annotation at the end of a line showing the author name, how long ago it changed, and the commit message.
Inline blame turns “who wrote this?” into a one-second answer.

My extensions list used to be 60 items long. VS Code took 11 seconds to start, half the extensions were fighting each other, and I couldn’t tell you what most of them did.

💥 Master AI & Tech Skills in 3 Months!
💰 One Subscription. Multiple Courses. More Savings.
🔥 Get Up to 50% OFF | ⏰ Limited-Time Offer
👉 Enroll Now & Start Learning

Press enter or click to view image in full size

Then I ran an experiment: disable everything, and only re-enable an extension the moment I actually miss it.

Seven survived. These are the ones I open every single day while working on .NET APIs, Angular front ends, and SQL databases. No themes, no icon packs, no “top 50 extensions” padding. Just tools that earn their place.

How I decide what stays

Before the list, my filter. An extension stays only if it passes at least two of these:

  • It saves me a context switch: I don’t have to leave the editor to do something.
  • It prevents a class of bugs: not just formatting, but real mistakes.

--

--

Experienced .NET and Angular developer passionate about building scalable web applications and sharing technical knowledge.