██████╗ ██╗███████╗██╗ ██╗ █████╗ ██████╗ ██╗ ██╗ ██╔══██╗██║██╔════╝██║ ██║██╔══██╗██╔══██╗██║ ██║ ██████╔╝██║███████╗███████║███████║██████╔╝███████║ ██╔══██╗██║╚════██║██╔══██║██╔══██║██╔══██╗██╔══██║ ██║ ██║██║███████║██║ ██║██║ ██║██████╔╝██║ ██║ ╚═╝ ╚═╝╚═╝╚══════╝╚═╝ ╚═╝╚═╝ ╚═╝╚═════╝╚═╝ ╚═╝
I learn in rabbit holes.
One interesting question becomes a tutorial, becomes a half-built side project, becomes three new things I'm now tracking in parallel. I've been doing this long enough to know it's not a flaw — most of what I actually know came from exactly this loop.
I'm a CS student who is not tied to a single stack. I enjoy understanding how things work and building across backend, cloud, DevOps, Android, and AI.
Off-screen: I think and read about psychology, watch a lot of film, and have opinions about things that have no business intersecting with software engineering — until they do.
Currently SDE Intern @ Cyborn, and working on a few things I genuinely care about.
If you're curious about what I've built, what I'm learning, or what I'm thinking about lately, you can find it all here:
⟢ working → SDE intern
⟢ building → serenity · privacy-first mental health platform for unis and some other side projects.
⟢ reading → somewhere between a distributed systems textbook
and something entirely unrelated
Most institutional software treats privacy as a policy. This one treats it as architecture. Admins can't read therapy notes or student journals — not because of a rule, but because of how the access control is built. Role-based permissions enforced at the database level. Designed to feel like support, not surveillance.
Jenkins → Ansible → Docker → Kubernetes → AWS. Built end-to-end to understand how the whole system actually connects — not just configure individual tools in isolation. Automated provisioning, container orchestration, the full cycle.
Engineered a production-style forecasting system that predicts market trends with Prophet, optimises portfolios, and explains insights through a natural-language AI assistant. Automated testing with CI/CD, deployed on the cloud, and backed by a persistent SQL data layer for reliable, reproducible financial intelligence.
| LANGUAGES | |
| BACKEND | |
| FRONTEND | |
| DATABASES | |
| DEVOPS | |
| CLOUD |
ec2 · s3 · rds · lambda · vpc · ecs · cloudwatch
|
| MONITORING |
nagios
|
| OTHER |
|
▍ off-screen
psychology · one rabbit hole
ai · definitely a rabbit hole
cinema · an unexpected rabbit hole
writing · where all the rabbit holes meet
· · · → into another rabbit hole · · ·
curiosity writes the roadmap. i just follow it.