Loading
About
I solve the problems that do not have a tutorial, and turn them into products people use.
Most software work is assembly: known problem, known library, known shape. I take the other kind. The brief where nobody can tell you up front whether it is even possible, where the answer has to be found rather than looked up, and where getting it working is only half the job because somebody still has to be able to use the thing at the end.
I work alone and end to end, which means the architecture, the schema, the infrastructure and the interface are decided by one person and actually fit together. Freelance from Delhi NCR, mostly remote, for clients in India, Japan and further out.
- 54
- merged open-source PRs
- 13
- open-source projects
- 5
- client products shipped
- 4
- languages in production
How I think about the work
Four things I will not trade away
Boring technology, interesting problems
The novelty budget goes into the problem, not the stack. Postgres, containers, a framework your next hire already knows. I would rather spend the difficulty allowance on your actual domain than on a database nobody can operate at 3am.
The hardest part first
Anyone can build the CRUD around the edges. I go straight at the thing that might not work, because a project that is going to fail should fail in week one, cheaply, while you still have options.
Say the uncomfortable thing early
If the plan is wrong, the estimate is optimistic, or the feature will not do what you hope, you hear it in a sentence, at the point where changing course is still free. Then I keep building.
It is not done until someone else can run it
Docs, a runbook, an architecture note and a handover. Code that only its author can operate is a liability you paid for, and I do not want to be a dependency you cannot replace.
Background
Open source is where I learned to read other people’s code
54 of my pull requests have been merged into 13 open-source projects, among them Qdrant’s Rust vector engine, Astral’s uv, Payload, react-email and mem0. Almost all of it is unglamorous correctness work: an unchecked integer conversion, a precedence bug in an assertion, a cursor that failed to round-trip across ISO week boundaries.
That habit is the most useful thing I bring to a client codebase. Landing a correct fix in a large unfamiliar repository, under someone else’s review standards, is exactly the skill of joining your project and being useful in the first week instead of the second month.
Every merged pull request, linkedWork with me
Fifteen minutes is usually enough to tell whether I am the right person for your problem. If I am not, I will say so and point you at what would be.