Model the hard part first.
If a product depends on routing, transactions or multi-service state, I make that logic explicit before polishing the happy path.
Who I am
Engineer by training.
Builder by habit.
The best product work makes the difficult parts legible. I like turning routing rules, transaction boundaries and multi-service workflows into interfaces people can understand and systems developers can reason about.
I build product interfaces and backend systems—from early flows to deployed software.
My degree gave me the fundamentals; building products taught me where those fundamentals become useful. I have worked across MERN applications, Symfony APIs, Flutter interfaces, FastAPI services, PostgreSQL, MongoDB and workflow automation.
See the work in contextWorking principles
How I make technical decisions.
Keep one source of truth.
The most reliable systems make ownership clear: the backend owns business rules, the ledger owns balances and the interface reflects state.
Make the result easy to read.
Good engineering should reduce cognitive load for the user and for the next developer who opens the project.
Beyond software
Portraits
in charcoal.
Professional portrait artistFor around five years
Away from software, I work professionally in charcoal portraiture. Each commission begins with a photograph, but the real work is translating likeness, light and character into a portrait that feels present on paper. The slower pace has sharpened my patience, observation and respect for small decisions.
Explore this aspectEducation
BS Computer Science
Bahauddin Zakariya University