Write code the next engineer can actually change
A full walkthrough of refactoring a real API handler, from separation of concerns and result types to transactions, tests, and the habits that keep code maintainable six months later.
Posted on
Full-Stack Software Engineer
Self-taught full-stack software engineer based in Nazipur, Naogaon, Bangladesh. I pick whatever tech the problem needs, whether that's backend systems, product-facing features, or AI that has to hold up in daily use.
I'm most useful when the problem is unclear and the system has to keep running anyway.
How I work
If you care more about outcomes than tools, this is the part that matters. I optimize for the business, the budget, and the traffic you'll actually have, then pick whatever gets you there.
I choose based on the problem, the timeline, and the budget, not on what I used last time. The stack serves the goal, never the other way around.
I size decisions to real load and realistic growth. No over-engineering for scale that isn't coming, no corners cut where it will hurt later.
Every choice has a cost: money, time to market, and the people who maintain it after me. I weigh those before I write a line of code.
Drop me into a new domain or an unfamiliar stack and I get productive quickly, then go deep enough to ship something sound.
My toolbox
Tools are means, not the point. When specifics matter, I usually start with a typed TypeScript backend and PostgreSQL, then widen the stack from there.
11 domains · 99 tools
Some of my writing
Notes on the things I think about - AI you can trust, systems that scale, and staying adaptable in a field that never sits still.
A full walkthrough of refactoring a real API handler, from separation of concerns and result types to transactions, tests, and the habits that keep code maintainable six months later.
Posted on
A deep guide to monoliths, microservices, queues, sagas, caching, and multi-tenant isolation, with real patterns from commerce and SaaS products that grew under load.
Posted on
A full database performance postmortem covering schema design, N+1, EXPLAIN plans, indexes, locks, pagination, connection pools, migrations, and when to denormalize.
Posted on
Let's build something
Tell me what you're building or where you're stuck. I read every message and reply personally.
Loading form…
Loading form…