Fourth-year CSE student, specialising in AI/ML.
I like the problems that start out as edge cases and quietly turn into the whole problem. Most of my time goes into rethinking the flow a user actually takes through a product rather than the one we assumed, and into writing code that stays reasonable as it grows.
Three surfaces over one backend, sketched in the header above. A merchant app for inventory, invoices, parties and vendors. A customer companion app showing invitations and per-shop invoice ledgers. One Express and Prisma backend on Postgres, with the same JWT shape across both apps so a single account works in either. Both clients are Flutter. Redis and MinIO sit behind it, all on Docker.
The parts worth the trouble have been the account-linking model between merchants and customers, the POS payment flows, and keeping the accounting auditable.
Languages and frameworks
 TypeScript |
 Dart |
 Flutter |
 React |
 Node.js |
 Express |
 Python |
Data and queues
 PostgreSQL |
 Prisma |
 Redis |
BullMQ |
 MinIO |
Infrastructure and hosting
 Docker |
 Nginx |
 Coolify |
 Cloudflare |
 SSH |
 Linux |
 Git |
Deployed with Coolify, reached over Cloudflare Tunnels and SSH. BullMQ and SSH have no brand mark of their own, so they borrow the Redis and shell glyphs.