Backend engineer by day. Open-source builder by night. Always chasing the problem nobody's solved cleanly yet.
I'm a 26-year-old SDE based in Mumbai, working remotely on production backend systems. I'm drawn to the parts of engineering that most people skip — how large codebases rot over time, why AI tools hallucinate in your repo, and what it would take to actually fix that.
Outside of code, I run, hit the gym, and think too much about systems — both the kind you deploy and the kind you use to run your life.
A few things that define how I work:
- I care more about why the code exists than what it does
- I build for the long game — open-source, in public, with real users in mind
- I'm currently learning to go from engineer to builder — and Loom is that bet
Most AI coding tools are blind to your codebase. They see files, not relationships. They miss why a function exists, what spec it implements, what breaks if you change it.
Loom fixes that — it's an open-source knowledge graph that connects your code and documentation into a single queryable graph. Built on tree-sitter, FalkorDB, and an MCP-native API.
- 🔗 Semantic search across code + docs simultaneously
- 💥 Blast radius analysis — know what breaks before you merge
- 📐 Drift detection — catch where code diverged from its spec
- 🤖 MCP-native — plugs straight into Cursor, Claude Code, and more
If you're working in a large codebase and want your AI assistant to actually understand it — ⭐ star Loom and follow along. It's being built in the open.