Identity
A student and builder who loves creating and experimenting — from cardboard crafts to code, games, and AI. This is the story of how I got here and where I'm going.
Developer · AI Builder
India
Current Mission
Building NEXUS AI — a self-hosted personal AI assistant that learns alongside me. I'm still learning development, AI, programming, cybersecurity, and the rest myself, and this portfolio documents that.
Origin
Long before code, I was making things. As a kid I built cardboard crafts inspired by things I was obsessed with — Ben 10, Beyblades, high-tech gadgets. I wanted the cool things I saw on screen, and buying wasn't always practical, so I learned to build them myself.
That habit stuck. I've always believed that if I can imagine something, I can try to make it real — first with cardboard and tape, later with code and game engines.
A chronological look at how I went from building cardboard gadgets to building an AI companion. Every step is real — including the ones that didn't go as planned.
Games
Games were my first way into building worlds. It started with a school competition — I needed to make something, so I made a game. That first project was Last Stand, a multiplayer FPS inspired by BGMI, built with Core Engine. Core was beginner-friendly and didn't require traditional coding, which mattered because I didn't have serious coding knowledge yet.
The competition presentation hit technical problems, and I didn't win. But that first loss is exactly what pushed me further — I went on to build Shadow Born in Unreal Engine 5.5, and that one took first prize.
I keep these because they're true. Each one is a step forward.
What happened
My first game competition presentation hit technical problems — and I didn't win.
What I did
I kept building and entered again with Shadow Born.
Lesson
Competition outcome isn't the measure; completing and shipping is.
Early YouTube videos did poorly — around 1,500 to 2,000 views each.
I kept making and improving my edits instead of quitting.
Consistency and patience matter more than any single video.
Building NEXUS on my own hardware means limited resources.
I design around what I have — self-hosted, private, and simple.
Constraints push you toward simpler, better architecture.
I don't learn mainly from formal courses — I learn by building real things and fixing what breaks. NEXUS is the best example: every version ships, every bug becomes a lesson, and progress is documented honestly rather than polished after the fact.
When I hit a problem I research, experiment, and iterate. Constraints — like building NEXUS on my own hardware — end up shaping the design, usually for the better.
I'm a student of all of this — none of it is mastered yet. Here's what I'm working with.
Currently learning
Experience
Strengths
Creative work
Video editing is another way I create and experiment. The channel started partly out of jealousy — watching classmates and bigger creators succeed made me want to try. Early videos got maybe 1,500–2,000 views, and that was a lesson in itself.
I stuck with it, learned to edit, and kept posting consistently. The channel has around 425 subscribers and my best Short crossed 136K views. It's a hobby, not a career — but it taught me the same lesson as everything else: experiment, fail, learn, persist.
Why I build
Technology, for me, is a way to think and work alongside something. That's the whole reason NEXUS exists — not to replace me, but to augment how I think, work, and create.
I value honesty (real statuses, no retroactive updates), privacy by design (my data stays on my hardware), and documented progress over polish.
Direction
Short-term: ship the next NEXUS version and keep documenting. Long-term, a vision — clearly labeled as vision, not current reality:
NEXUS is still in development. Everything above is where I'm headed, not what's finished.
My long-term attempt to build the personal AI companion I've imagined since childhood. A self-hosted personal AI assistant — an integration layer between LLMs, memory, and automation tools.
The site you're on right now — built to document my work and to be a real artifact of the stack I'm learning.
The projects are the evidence — NEXUS and the games, documented honestly. The dev log shows how it actually happens, one version at a time.