My Developer Setup in 2026

A good developer setup is not about having the most tools. It is about having a workflow that feels fast, reliable, and easy to return to every day. Over time, I have tried to keep my setup simple and focused.

Editor

My main editor is VS Code. I like it because it is lightweight, customizable, and works well across different kinds of projects. Whether I am writing TypeScript, Markdown, backend code, or documentation, VS Code gives me a comfortable default environment.

Some extensions I usually rely on are:

ESLint
Prettier
Astro
Tailwind CSS IntelliSense
GitLens
Markdown preview tools

Terminal

I prefer using a clean terminal setup with simple aliases for common commands. I do not try to over-customize it too much, because I want the same commands to work across machines and environments.

For example, a few common commands in my daily workflow are:

npm run dev
npm run build
git status
git checkout -b feature/new-work

Workflow

My workflow usually starts with understanding the problem clearly before writing code. I try to break work into smaller pieces, make one meaningful change at a time, and keep commits readable.

I also use documentation as part of my workflow. If I solve something tricky, I try to write it down either in the project README, a note, or a blog post. This helps me avoid solving the same problem again from scratch.

Productivity

The biggest productivity improvement for me is reducing context switching. I try to keep my editor, terminal, browser, and notes organized around the task I am working on.

A few habits that help:

Keep branches small and focused
Run builds before pushing changes
Write down decisions while they are fresh
Avoid adding tools unless they clearly improve the workflow

Final Thoughts

My setup is still evolving, but the principle stays the same: use tools that reduce friction and help you think clearly. The best setup is the one that lets you spend more time solving problems and less time fighting your environment.