What I Learned: Building My First VS Code Extension (As a Designer Who Did Not Mean to Do This)

I never meant to build a VS Code extension, but one small idea about catching content mistakes in pull requests sent me down a wonderfully chaotic path.

Along the way, I learned more about automation, developer tooling, and my own capabilities than I expected—and it completely changed how I see my role as a designer.

Content errors kept sneaking into the product—typos, lorem ipsum, TODOs, little things that somehow make it all the way to the finish line. And content reviews? They always seemed to happen at the very end, when no one has time and everyone is tired.

So I started wondering:

“What if we could catch this stuff automatically, before anyone even notices it’s wrong?”

That’s how a small idea snowballed into a surprisingly powerful workflow tool… and a lot of personal growth along the way.

Read the Medium Article