I write the error message before the happy path.
Story
At work, that’s flight and travel platforms. On my own time it’s mostly tools for the work itself: a Chrome extension that catches the API calls DevTools misses, and a VS Code extension that finds the component behind a class list. That one has passed 4,000 downloads.
I fuss over how things move and respond: which way a panel slides, how a list settles when you stop scrolling, what a button does in the half-second after you press it. This page is mostly that kind of fussing.
Off the clock: games, getting outdoors, and learning things I’ll probably never need.
Innovate SolutionAssociate software engineer · Dhaka
Production features for B2B and B2C flight and travel platforms, demo sites for client pitches, and faster pages.TaskirsViewFull-stack developer, intern · China
Helped plan the architecture of a new internal collaboration platform, and designed and integrated its REST APIs.
House rules, marked up01 / 04
Most people meet a screen in a state nobody drew: the answer was “no”, the row is still saving, the request failed while they were already typing the next thing. So I draw those first, and the version where everything works comes after.
NetLensa call that dies before it answers still gets its row, marked ERR.
It shows where something came from, keeps your place through a change, or tells you the system heard you. A movement that does none of those still costs frames and attention, so it gets cut.
This pageeach sheet slides over the last, so you always know which way you came.
The database driver, the auth library, the date maths: under a product I want dependencies that have never surprised anyone. If something has to be new and risky, it should be something a visitor can see.
Expresslanemoved from MongoDB to PostgreSQL with Prisma, so the database itself rejects bad data.
Every technical decision trades something away. Smooth scrolling costs you the browser’s native scroll. A pinned section costs you a predictable page height. Not writing down what a decision cost is how a codebase ends up with three of them quietly fighting each other.
smart-class-lookupparsing runs on worker threads capped at half the cores, and each carries its own copy of Babel, so they are torn down when the index is built.
Working on something that has to hold up?
Write to[email protected]
Email is fastest: I answer within a day. Dhaka, GMT+6.
-640.webp)
