Feb 20, 2026 · 12 min read · Planning / Best Practices / Architecture
My Developer Setup (Tools I Use Daily)


Every developer has that moment.
You get a new project idea…
You open VS Code…
You create a new folder…
And then suddenly you're stuck thinking:
"Wait… how should I actually start this?"
Most beginners skip planning and jump straight into coding. They write random files, add random features, and after a few days the project becomes a beautiful mess of confusion.
Experienced developers do something different.
They rely on a toolkit and workflow that helps them plan, build, and ship projects efficiently.
So in this article, I'll share the tools I use daily when building a project and how they help me stay organized.
1. VS Code – My Coding Environment
Of course, everything starts with VS Code.
It's fast, customizable, and has an incredible extension ecosystem.
Some of the extensions I use daily include:
- Prettier – automatic code formatting
- ESLint – keeps code clean
- GitLens – better Git insights
- Tailwind IntelliSense – auto-suggestions for Tailwind classes
VS Code is basically the home base where most of the development happens.
2. Notion – My Project Brain
Before writing code, I like to organize my thoughts.
For that, I use Notion.
Inside Notion I create a page for every project and document things like:
- the purpose of the project
- features I want to build
- page structure
- ideas for improvements
Why?
Because after two weeks you will forget half your ideas.
Notion helps keep everything structured and clear.
3. Excalidraw – Planning the Architecture
Once the idea is clear, I move to Excalidraw.
It's a simple tool for sketching diagrams and flows.
Here I usually draw:
- page flows
- component hierarchy
- database relationships
- API structure
This step might feel unnecessary at first, but it saves a lot of confusion later.
Instead of guessing how things connect, I already see the structure before coding.
4. Figma – Quick UI Prototypes
Sometimes I design the interface before coding.
For that I use Figma.
I'm not a designer, so my goal isn't to create a Dribbble masterpiece.
I just design basic layouts like:
- homepage
- dashboard
- navigation
- forms
Even a simple wireframe makes development much easier.
And if I'm feeling lazy… I skip this step and design while coding (don't tell designers).
5. MongoDB / Neon – My Databases
For storing data I usually choose between:
MongoDB
Great for flexible NoSQL data structures.
Neon (PostgreSQL)
A modern serverless SQL database that works well for production apps.
Both are easy to deploy and integrate with modern frameworks.
6. Clerk / Firebase – Authentication
Authentication can quickly become complicated.
Instead of building it from scratch, I usually use:
- Clerk – modern and developer-friendly
- Firebase Auth – widely used and reliable
These tools save hours of work and let me focus on building the core features.
7. Postman / Thunder Client – API Testing
When building backend APIs, testing endpoints is essential.
For that I use:
- Postman
- Thunder Client (inside VS Code)
They help me test:
- API requests
- responses
- authentication
- error cases
It's much easier to debug APIs here before connecting them to the frontend.
8. GitHub – Version Control
Every project goes on GitHub.
Even personal projects.
GitHub helps with:
- version control
- backups
- collaboration
- showcasing projects in your portfolio
Plus, a clean GitHub profile always looks good to recruiters.
9. Vercel – Deployment
Once the project is ready, I deploy it using Vercel.
Why Vercel?
- easy Next.js deployment
- automatic builds
- fast global CDN
- simple domain setup
Deployment becomes almost effortless.
Push to GitHub → Vercel deploys automatically.
Final Thoughts
Your developer setup isn't about having the most tools.
It's about having the right workflow.
For me, the process looks like this:
Idea → Plan in Notion → Architecture in Excalidraw → UI in Figma → Code in VS Code → Test APIs → Deploy on Vercel.
This workflow helps me stay organized and actually finish projects instead of abandoning them halfway.
Because at the end of the day…
Anyone can start a project.
But finishing one properly?
That's what makes a developer stand out.