More than just
code.
Backend logic should be invisible, and frontend design should be intuitive. Everything else on this page follows from that.
Backend logic should be invisible, and frontend design should be intuitive. Everything else on this page follows from that.
JS Web Devs is Md. Jamil Shikder — a full-stack developer and RUET Computer Science graduate who treats code as a medium for solving real problems rather than an end in itself. One person designs the data model, writes the API, builds the interface, and is still there once it is live.
Most of the work is bridging the gap between a business requirement and its technical execution: scalable marketplaces, real-time platforms, stores and the everyday sites that simply have to keep working. The common thread is clean architecture and system design chosen at the start, when it is still cheap to change.
Performance is a feature, not an afterthought. Core Web Vitals and sub-second load times are part of the brief from the first commit, not a clean-up pass at the end. Roughly three years of client work so far, mostly on the MERN stack and modern deployment workflows.
It began as curiosity about how the internet actually worked. That turned into an interest in MERN stack architecture and in content systems flexible enough to survive the second year of a project.
Today the focus is helping businesses grow their digital presence, with performance, SEO and user experience as the measures that matter. A complex SaaS platform and a single high-converting landing page are judged the same way: by what they do in the real world.
HTML, CSS and responsive layout, then React, Next.js, Tailwind CSS, Framer Motion and Vite for the parts that need to move.
Node.js with Express or NestJS, Mongoose, JWT authentication and REST APIs behind a contract that stays stable.
MongoDB and PostgreSQL, plus managed options like Supabase and Firebase when they shorten the path to launch.
WordPress and Shopify where a content or commerce platform is the right answer, with Git, GitHub, Docker, Cloudinary and Vercel around them.
Core Web Vitals, Lighthouse audits, lazy loading and SEO — measured before and after, not assumed.
LLM integration, web scraping and n8n workflows for the repetitive work that should not need a person watching it.
Every project gets treated like my own business, which mostly means optimising for longevity instead of for the fastest possible handover.
Modular, scalable and documented architecture — written so the next change is cheap, whoever makes it.
Deadlines treated as commitments, with clear communication at each milestone rather than silence and a surprise.
The relationship does not end at deployment. Launch is the point where the site starts needing attention, not the point where it stops.
Prefer a brief? Send it through the contact form.
Tell me what you are building and what is in the way. You will get a reply from the person who would do the work, not a sales desk.
Start a project