proof of work.
17 months. Sep 2024 → Feb 2026. Everything I shipped at Foyer / Merlin AI — raw, unfiltered, pulled directly from GitHub. No fluff.
the story behind the stats
I was in my first year of college, living in a hostel with my brother. We didn't have much going on — just classes, hostel life, and a lot of YouTube. One evening I stumbled across a browser extension called Harpa AI. The moment I saw what it could do, something clicked in my head — I couldn't believe this kind of thing existed. I immediately called my brother over to show him. He was blown away too. He asked me the name — but I refused to tell him. I wanted him to find it himself. So he searched, and instead of Harpa, he landed on Merlin AI. That was the first time I ever saw that name. Neither of us knew it would mean anything to me.
Fast forward to August 1st, 2024. I applied to Merlin AI. Formally, through the proper channel, like everyone else. The application expired without a response. That was that. I moved on.
Then on September 10th, 2024 at 3:26 PM — I was walking back from my college classes to my hostel, just a regular afternoon — my phone buzzed. It was a message from Siddhartha sir, the CTO at Foyer Work, reaching out for an interview. Not a recruiter. Not an automated email. The CTO personally. Of the same company that had already let my application expire 40 days earlier. I still cannot fully describe what I felt in that moment. I had been genuinely praying — not just hoping, actually praying — for any kind of work. Freelance, unpaid, coffee money, anything. I just wanted to build something real for someone. And out of nowhere, this message arrived. The interview was the next day. I barely slept. I wasn't confident — I had no idea if I was good enough. But I got in.
Now here's the part that actually matters.
From the very first day, writing code for Merlin never felt like work. I don't know how else to say it — it just didn't. While other people clocked out, I was opening my laptop. Not because anyone told me to. Not because there was a deadline breathing down my neck. But because I was in the middle of a problem and leaving it felt physically wrong.
I remember the night I built the AskMerlinAI Twitter bot. It got assigned to me at around 11:30 PM. By the next morning, it was done and live. That night wasn't unusual — it was just one I happen to remember clearly.
There were nights migrating entire codebases from one platform to another, alone, at 3 AM, when the rest of the world was asleep. Nights where I'd start on something small and look up at 5 AM wondering where the time went. I wasn't grinding. I was genuinely absorbed. There's a difference — and I felt it every single time.
My goal from the very beginning was never to just ship things. It was to ship things that actually matter — features that real users would feel, improvements that moved the product forward in ways that counted. Every time I opened a PR, I wasn't thinking about adding to a number. I was thinking about the person on the other side who was going to use what I just built.
I've shipped features I'm genuinely proud of. Deep Research, Thine, Tool Orchestrator, Crafts, Streaks — these aren't items on a list to me. I remember exactly where I was when I first understood the problem, exactly what it felt like when it finally worked, exactly how many times I tore it down and rebuilt it because the first version wasn't good enough yet.
The stats below aren't something you can manufacture. You cannot push 329 PRs across 14 repos in 17 months on obligation alone. Obligation runs out. It runs out at 6 PM, it runs out on weekends, it runs out the moment nobody is watching. What you see below is what's left when you genuinely cannot stop.
These aren't numbers. This is just what makes me happy.
activity timeline
PRs opened per month — every spike is a product launch, every dip is me switching to something new
Each orange bar is a story. January 2025 — Streaks and Essay Writer shipping simultaneously across 4 codebases. April 2025 — Deep Research Interactive UI, 35,683 lines in a single month. September 2025 — bootstrapping Thine from zero, 51,430 lines. The dips aren't laziness — they're me switching domains, learning a new stack, and building up momentum for the next spike.
thine contributor ranking
Thine is an ambient personal AI iOS app built by the Merlin team — always listening in the background, building a living memory of your life and work, and proactively surfacing patterns you would've missed. One of the hardest engineering problems in personal AI right now.
I spent four months building the foundation of this product from scratch — the knowledge graph, the realtime agent, the memory pipelines. Then I moved on to Merlin again. I haven't committed to this repo in 2 months. Still sitting at #2 out of the entire team.
features owned
each bar = total PRs. built from scratch, maintained, iterated.
Every single one of these started as a task someone assigned me. Every single one became something I obsessed over. Deep Research has 36 PRs because I kept going back to it — fixing, improving, rethinking the architecture — long after "done" would have been acceptable. Thine has 43 PRs because me and my team built an entire new product from zero together. Crafts has been running for 15 months and I'm still not finished with it. These aren't checkboxes — they're things I actually cared about.
career arc
UI badge fixes → AI systems engineering. 8 phases, 17 months.
I didn't plan this progression. I just kept building whatever was in front of me. In September 2024, I was fixing UI badge queries — literally the smallest possible thing. By February 2026, I was designing tool orchestration systems that recover from LLM hallucinations at runtime and managing context windows across different user plan tiers. That gap didn't happen gradually. It happened in sprints — each phase pushing me into something I had never done before.
PR insights
how I work — speed, size, commit density
merge speed
74% same-day. That's not just speed for the sake of it — that's writing PRs that are scoped enough to review and ship without back-and-forth. The 2.3-day average is skewed by the Deep Research marathon PRs. The real number is 0.1 days. Same day, almost always.
PR size distribution
56% of my PRs are XS or S — surgical, focused, in-and-out. The XL and XXL PRs aren't sloppy — they're deliberate. They correspond exactly to the bootstrap moments and major feature launches. Big PR = big thing being built, not big mess being cleaned up.
commits per PR
Went from fixing UI badges in Sep 2024 to designing AI tool orchestration systems, building memory graphs, shipping agentic research pipelines, and bootstrapping an entirely new product — all in 17 months. The PR history doesn't lie.
I didn't have a 5-year plan. I didn't have a strategy. I had a hostel room, a laptop, and a message from a CTO that arrived at 3:26 PM on September 10, 2024. Everything else is just what happened when you take that seriously every single day.