Journey
The long version of the homepage’s day: where I’m from, the turn in June 2024, the teaching, the work, and where I’m heading — each stop described by what was built and what changed.
Where it starts
Braj
I’m from Braj, the region of India around Mathura and Vrindavan — the place Mero Braj later set out to map.
June 2024
The best investment I made
It wasn’t in the stock market. It was in myself.
From August ’24 it was the same desk, the same books, the same machine, oats and coffee. For an entire year, nothing changed.
Odoo Combat Hackathon 2024 · Ranked in the top 1%
Aug 2024 – 2026
Teaching computer science
Let’s Unbound
- Delivered 500+ hours of live Python and Java instruction to US AP Computer Science students.
- Designed project-based curricula, so students shipped working software rather than only passing exams.
- hours of live teaching
- 500+
Python · Java · Curriculum design
2024 – 25
A museum for home
Braj’s heritage is spread across an entire region and barely documented online. The goal was one place to explore it, without needing a high-end device or a fast connection.
It has had two versions. What follows is the first, the grant-era build; merobraj.org today runs a later, lighter rebuild.
Mero Braj
Grant-funded heritage platform
- Wrote the proposal and secured grant funding.
- Led a team of four to build its first version: a 3D map and 360° tours for 100+ heritage sites.
- Built for low-end phones: lazy-loaded media and a modular architecture.
Three.js · Next.js · GraphQL · MongoDB
July 2025
devDocs on PyPI
On a big, old, undocumented project, what should have taken a day stretched into a week — just because no one had the time (or patience) to write documentation.
devDocs came out of that: a command-line tool that writes Markdown documentation beside the code.
- downloads on PyPI, all versions
- 6.1k
- All-time total from pepy.tech, which also counts mirrors and CI installs. Six releases since July 2025.
2025
The year I got started for real
A zero to one shift: I built solid habits, took ownership, and stopped waiting for motivation — I started showing up instead.
Devslane
Client products across web, mobile and AI · 2025 – now
- Client-billable projects, wearing whichever hat the work needs: full-stack web, cross-platform apps in Flutter, AdonisJS back ends on PostgreSQL and Socket.io, RAG and AI features — and the system designs behind them.
- CRM and ERP products, including owning the client-onboarding module of a live ERP.
- A payments proof of concept that established production feasibility, and a Storybook component library now used across teams.
TypeScript · React · Flutter · Node.js · AdonisJS · PostgreSQL · Socket.io · Redis · Storybook
Legal-tech client
A legal-AI platform: retrieval, architecture and sign-in · 2025
The client isn’t named here.
- Cut information-retrieval latency by 40% with targeted query and architecture changes.
- Refactored core Next.js and NestJS modules to simplify data flow and reduce coupling.
- Rebuilt authentication end to end on Clerk — 50% fewer login failures and faster onboarding.
- faster retrieval
- 40%
- fewer login failures
- 50%
Next.js · NestJS · TypeScript · Clerk
Trade It Up
in progressA rules-first momentum allocation engine across equity, gold and cash.
- over 20 years, in backtest
- ~10×
- Read off my own backtest chart, posted in August 2025; Nifty 50 ended near 12× and gold near 8× over the same years. Not a forecast.
2026
Stuti, dts-tracer and devDocs v4
Stuti
in progressA desktop assistant with memory and web search — on its way to an agent that can talk, and act with your permission.
dts-tracer
Policy-based request tracing for Express, in one line of middleware.
devDocs
v4 in progressA CLI that documents a whole codebase — now being rebuilt to spend tokens only where they buy understanding.
Now · Oct 2026
Where I’m heading
For now, it runs through what’s on my bench:
- devDocs v4 — a dependency-free engine that plans before it prompts
- Stuti — a desktop assistant learning to talk, and to act with permission
- This site — ink, paper and a pond
Next
Your project, perhaps.
Tell me what you’re building and where it hurts. One email is enough to start.
Listen. Understand the problem, the people and the constraints before touching a line of code.
Sketch the system. Draw it first — data, boundaries, failure modes — and agree on it together.
Build in the open. Small, reviewable steps with a working version early and visible progress every week.
Hand over cleanly. Documentation, tests and a walkthrough, so your team owns it from day one.
Open to new projects · Replies within 24 hours · IST (UTC+5:30)