I'm a final-year CS student with a deep focus on backend systems, real-time protocols, and infrastructure. But the honest version is simpler: I build things because I can't stop asking how they work.
My journey started with wanting to understand how the web actually works — not just building CRUD apps, but diving into , WebSocket protocols, video streaming pipelines, and distributed systems. I built EazyCam because I wanted to understand how real-time video actually moves between devices — wired and wirelessly. I built Who's There because I wanted to feel what sub-400ms message delivery means architecturally, not just read about it. I built ProjectPals because finding the right collaborator in college was genuinely broken, and 45+ students ended up using what I made. That same curiosity is why..?
I started a YouTube channel. I explain backend systems, how the internet infrastructure works not to grow an audience, but because explaining something clearly is the hardest test of whether you actually understand it. 4200+ views so far.
I pick up tools as I need them. The question comes first, the framework second.
Timeline
-
2025 — PresentFinal Year — Started Youtube, building DroppActively building, writing, and looking for backend / DevOps roles where I can ship meaningful work.
-
2025Built EazyCam & ProjectPalsTackled WebRTC P2P streaming and real-time collaboration at scale — two of my most technically complex projects.
-
2024Who's There & UnrushDeep dives into WebSocket architecture, Redis pub/sub, and large file storage systems deployed on AWS.
-
2022-23Started CS DegreeBegan formal studies. Quickly realized the real learning was outside the classroom — and started building.