Amit
Das.

Developer. I build for the web.

I'm a developer studying at Metropolitan University. I build fast, accessible web products, from the screens people use to the APIs and data behind them.

01

About

I'm Amit Das, a developer studying at Metropolitan University. I care as much about how a product feels as how it's built. Most of what I make loads fast, works properly with a keyboard or a screen reader, and does what it says it does.

Day to day, I build web applications end to end, from the database up to the front end. I like small codebases with tests I can trust, and I'd rather put an early version in front of real people than polish it in private for months.

When I'm not building, I read other people's code and take apart designs I admire to work out why they feel right.

Full stack
Everything from the interface down to the database
Accessibility
Keyboard navigation, focus states, and contrast, checked before I call anything finished
Performance
Rough budgets for page weight and load time, set at the start of a project
02

Selected Work

log-planner-xfanatics.web.app

Log Planner ↗

Live

A planner web app for logging work and planning ahead. It's live, and anyone can open it and use it. Shipping it taught me the unglamorous parts of running a real product: deploying, fixing things once people are actually using them, and keeping it fast.

Web AppPlannerFirebase HostingLive
Discuss a project like this →
03

Education

School exam results, listed for reference. I'm currently studying at Metropolitan University.

PSC

Primary School Certificate

GPA 5.00

JSC

Junior School Certificate

GPA 5.00

SSC

Secondary School Certificate

GPA 5.00

HSC

Higher Secondary Certificate

GPA 5.00
04

Expertise

Front End

Pages that load fast and stay usable on any device, whether someone is on a phone, a slow connection, or navigating by keyboard.

TypeScriptReactNext.jsCSS ArchitectureAccessibility

Back End & Data

APIs and data models that stay predictable, so changing them later doesn't break things. Boring, in the good way.

Node.jsPostgreSQLREST & GraphQLAuthCaching

Performance

I profile slow pages, set budgets for load time and bundle size, and fix the bottlenecks that actually show up.

Core Web VitalsEdge RenderingProfilingBundle Budgets

Process

Small commits, realistic estimates, and notes written for whoever picks the project up next.

TestingCI / CDCode ReviewTechnical Writing
i.

Start small

A small working version in real hands teaches more than a big plan in a document. I build narrow first, then widen it once I know what people actually need.

ii.

Accessibility is part of the job

If someone can't use it, it isn't finished. Keyboard paths, focus states, and contrast belong in the first version, not in a later fix.

iii.

Leave the code tidier than I found it

Every change should make the next one easier: clearer names, fewer surprises, and tests where they earn their keep.

World clock

Dhaka--:--:-- 
London--:--:-- 
Berlin--:--:-- 
New York--:--:-- 
Melbourne--:--:-- 
Riyadh--:--:-- 
05

Contact

Start with a short brief

Pick what you're building and add a line or two about it. Then copy the brief and send it wherever you reach me. It stays in your own messages, so nothing gets lost in a spam folder.

Copied. Paste it into any message.