Building stuff on the web can get messy fast if you don’t have a solid workflow.

Over time, I’ve figured out what works for me. This post breaks down the tools I use when working on web projects — from writing code to deploying it — and why I stick with them.

✍️ Code Editor – VS Code

This one’s obvious. VS Code is lightweight, fast, and has tons of extensions. I use it for everything — frontend, backend, and all that good stuff.

Extensions I can’t live without:

• Prettier – Auto-formats my code so I don’t have to argue with myself about spaces and tabs.
• ESLint – Catches stupid mistakes before they become real problems.
• Tailwind IntelliSense – Shows class suggestions when I write Tailwind CSS. Saves time and memory.

🌐 Framework – Next.js

Most of the sites I build are with Next.js. It gives me:

• File based Routing out of the box
• Server-side rendering and Static Genertation when i need it. This blog post you’re reading? It’s statically generated. That means it’s pre-built for speed. But when I need changes, I tap into the power of on-demand revalidation, so updates go live without waiting for a full rebuild. Feels like magic, works like logic
• Automatic image optimization
• API Routes: Next.js allows me to create serverless functions directly within my application using API routes, simplifying backend integration.

🎨 Styling – Tailwind CSS

I used to hate writing CSS until I found Tailwind CSS. It’s just faster. I don’t have to come up with class names like header-content-box anymore. I just write the styles right in the HTML and keep moving.

Some people think it’s ugly. I think it’s clean, because I actually finish stuff now.

🔐 Auth – NextAuth or Kinde

If I need auth, I pick based on how much control I want.

• NextAuth – when I want something fully customizable and I’m okay setting up the details.
• Kinde – when I just want auth handled for me and don’t feel like fighting with OAuth flows.

Both work well with server-side frameworks like Hono or Next.js.

Lately, Better-Auth has been popping off too — I might look into it when I’ve got some time.

🧠 Backend – Node.js + Hono.js

When I’m not using something like Next’s API routes, I usually go with:

• Node.js – Simple and fast for backend stuff.
• Hono.js – A lightweight framework for building APIs. Think Express, but smaller and faster.

🗃️ Database – PostgreSQL + Prisma

• PostgreSQL – Solid relational database. Does the job.
• Prisma – Makes querying the database feel like cheating. The auto-complete is crazy good. Plus, it takes care of migrations and makes working with the DB way less painful.

📦 Package Manager – pnpm

I use pnpm instead of npm or yarn. It’s faster and saves disk space. Once you try it, there’s no going back.

🔄 Version Control – Git + GitHub

Nothing fancy here. I use Git for version control and GitHub for hosting code.

🚀 Deployment – Vercel

For frontend projects, Vercel is the easiest deployment experience I’ve had. Connect your GitHub repo, and it auto-deploys every push to main. Done.

For backend APIs, I usually deploy on Render, Railway, or a VPS depending on how serious the project is.

🧪 Testing – Kinda Skipped (For Now)

To be honest, I don’t write a lot of tests yet. Not proud of that, just being real. When I do test stuff, it’s mostly manual or small unit tests using Vitest or Jest. I’ll get better at this. Baby steps.

🖼️ Design – Figma

I’m not a designer, but I use Figma to:

• Mock up layouts before building
• Grab assets and icons
• Share ideas visually if I’m collaborating with anyone

Sometimes I just freestyle in code. Depends on the vibe.

Final Thoughts

This isn’t the only “correct” workflow — it’s just what works for me right now. I’m always tweaking things, swapping tools, or learning something new. If you’re trying to build your own workflow, start with what feels right and improve from there.

If you have a better tool or trick that makes your workflow smoother, I’m all ears.