A short biography of someone who refuses to pick a lane.
Discipline
As of September 2026 I am a Master's student in Computer Science & Engineering at DTU, Copenhagen — coursework now, a thesis still finding its shape. Before the move, I was a software engineer — shipping into a component library used inside Apple, authoring framework-agnostic Web Components, building Node and Laravel services behind dashboards nobody sees, and packaging TypeScript primitives that other teams import and forget. That contract, via Softzino Technologies, closed in August 2026, cleanly, ahead of term starting. The work was mostly unglamorous and that was the point. Good software is a long series of small, careful decisions made in sequence.
By some nights and weekends I am a published researcher — a convolutional neural network for plant-disease classification, 55,000 images, 39 classes, 98.7% validation accuracy, and a paper in IJEECS Vol. 28, No. 3. The habits are different. Research asks you to be wrong slowly and in writing. Engineering asks you to ship by Friday. I find the tension productive.
Surface Area
A working inventory of the terrain I actually cover, not a skills cloud. Updated whenever something ships.
| Category | Primary | Since | Notes |
|---|---|---|---|
| Frontend | Vue 3 · Nuxt 3/4 · React · Web Components · TypeScript · SCSS · Pinia | 2020 | Component libraries, design systems, framework-agnostic primitives. |
| Packages | TypeScript · Rollup · StencilJS · Web Components | 2023 | Framework-agnostic primitives; tokens as public API. |
| Backend | Node · Express · Laravel · Sequelize · Postgres · Mongo | 2019 | Internal APIs, dashboards, payroll and field-service domains. |
| Research | Python · TensorFlow · Keras · OpenCV · CNNs | 2021 | One published paper. |
| Tooling | Claude Code · Vite · pnpm · Git · CI on Vercel, Netlify | 2024 | Shipping fast; treating the agent as a senior pair. |
Fieldwork
2015 — 2019
Before the code, there were the hills. For roughly four years I worked as a guide through Bandarban, Rangamati, Sylhet, and Sunamganj — long days on uncertain trails, reading maps, learning which river crossings were safe that week.
The connection, in retrospect, isn't poetic — it's procedural. You learn to survey unfamiliar terrain, take honest notes, mark what's stable and what isn't, and hand the document to whoever follows. The job has a different name now.²
² The habit of careful documentation was first formed somewhere between a river crossing in Sunamganj and a trail notebook that got rained on. It turns out to be the same habit a senior engineer uses to write a migration plan.