A few things that
got me here.
None of it arrived in a straight line. That might be why I kept going.
SCHOOLJARVIS was ambitious.
I tried building a personal assistant. The ambition was slightly ahead of the Python.
Read chapterClose chapter
Iron Man sent me towards Python and a personal-assistant project. I wrote some code and reached a point where I couldn't take it further. I didn't yet know enough, or how to learn what was missing. I left it unfinished.
That's where this story starts: an idea much bigger than my ability at the time.
FIRST YEARCode. Cuts. A client brief.
Video editing, competitive programming, and a founder who needed a product video.
Read chapterClose chapter
I spent the year learning video editing and storytelling alongside coding, competitive programming, and DSA. A startup founder asked me to work on a product video for his Y Combinator application.
It was my first taste of a different brief: someone else had a product they needed to explain, and I had to work within that goal.
SECOND YEARRead the review.
One open-source proposal was withdrawn. Another merged. Both changed how I read a PR.
Read chapterClose chapter
At Daffodil, developers who knew the project questioned where logic belonged, which behaviour had to stay, and whether a new option was needed at all.
One proposed configuration change was withdrawn after review. Another contribution merged after its error handling was revised. Those reviews showed me what a useful pull request asks of its author.
OCTOBER 2025The course ended. The project didn't.
Runiverse began in a five-person college team. Three of us kept building.
Read chapterClose chapter
The original idea came from our course team. After submission, I wanted to keep going. Meet Dhorajiya, Daksh Amalseda, and I did.
I led activity tracking and territory engineering. We tested in open beta, reached runners through our network, and kept finding problems worth working through. I wanted a challenge whose entire answer wasn't visible at the start.
NOWStill reserved. Now representing a company.
The work grew from code into runners, collaborators, and conversations I once avoided.
Read chapterClose chapter
I'm in my third year. I'm still more reserved than outgoing, but I can feel the change in conversations I can have.
Explaining Runiverse to a runner, a collaborator, and an investor takes different language. I'm learning how to be clear, discuss the stakes, and represent the company. Some things that felt impossible a year ago are now ordinary parts of the work.