How I build
- PlanWhat it has to do, where the boundaries go, and how the work splits across the team.Requirements, architecture, task breakdown
- InfrastructureSet up first, so every deploy after it runs the same way.Docker, GitHub Actions, Coolify, Vercel, Cloudflare
- DataTables and the rules between them, validated before anything is saved.PostgreSQL, Drizzle, Prisma, Zod
- APIThe contract the interface talks to, with auth and access control built in.NestJS, Express, JWT, Google OAuth, CSRF, RBAC
- InterfaceThe screens people use, built on the API beneath them.Next.js, React, Tailwind CSS, shadcn/ui, RTK Query
Work
Dashboard
Media library
Drag-and-drop uploads, virtualized grids and a reusable picker over a Cloudinary-backed API.
- InterfaceNext.js 16, virtual scrolling
- APINestJS, Cloudinary
- DataPostgreSQL, Drizzle
- InfrastructureVercel, Cloudinary
Workflow
Task manager
Role-based tasks that move through a fixed status order, with a full audit trail.
- InterfaceNext.js, RTK Query
- APINestJS, JWT and sessions, CSRF
- DataPostgreSQL, audit log
npm package
chat-scroll-behavior
Scroll logic for chat interfaces: loads history in both directions and keeps the viewport steady.
- InterfaceTypeScript, React, vanilla JS
- Infrastructurenpm

About
I start every product on paper: what it has to do, where the boundaries go, and who builds which part. Then I build it layer by layer, review every change that goes in, and teach the people working with me to do the same.
Experience
- 2026Software Engineer and Team LeadTypeTech IT
- 2023–25Full Stack DeveloperTypeTech IT
- 2020–23Freelance Web DeveloperFiverr and direct clients
Education
- B.Sc.Electronics and Communication EngineeringNational University
- 2015HSC, Science, GPA 5.00Cambrian School and College
- 2013SSC, Science, GPA 5.00Ahsania Mission School and College



