Member-only story

🏗️ VSCode Macros Saved Me From 1000s Of Seconds Of Misery

Tom Smykowski
4 min readJul 2, 2024

--

Between manual editing and AI, there’s a place for automated code editing without quirky effects and tediousness

As you maybe know, I use mostly VSCode for my coding.

There’s several reasons for that, but the most important for me is customisability.

Usually I work on complex projects. To work productively and moderately enjoying it, you have to have a toolset that helps you.

VSCode offers a lot of extensions and options for that. I’m not forced to use this or that.

In case where I need to manage a vast codebase with a lot of connections and conventions it’s easy to miss some. It’s caused by two things:

  • no way to document all code level requirements and conventions
  • manual code editing

The first problem is caused by conventions on a project by project basis. For example:

You have a web project that uses Tailwind. I could stop here. But let’s go further. You define custom mixins for styles. Now, you can’t use CSS names, you have to use project specific names. These names aren’t displayed in the browser, so you have to mentally translate all Tailwind aliases back and forth…

--

--

Tom Smykowski
Tom Smykowski

Written by Tom Smykowski

🚀 Senior/Lead Frontend Engineer | Angular · Vue.js · React | Design Systems, UI/UX | Looking for a new project! 📩 contact@tomasz-smykowski.com

No responses yet