Get in touch
Whether you have a project in mind, spotted a mistake in an article, or want a tool that does not exist yet — this is the place. Messages go straight to my inbox and I answer most of them within two business days.
Based in Jaipur, Rajasthan, India (IST, UTC+5:30). Available remotely worldwide.
Typical reply time: within two business days.
Send a message
The more context you give, the more useful the reply will be. There is a simple sum at the bottom of the form to keep spam out — no third-party tracking scripts are used.
What to write about
Every message is read personally — there is no support team and no automated triage behind this form. A few lines of context about what you are trying to do makes the difference between a generic answer and a genuinely useful one.
Project & consulting enquiries
Architecture reviews, contract engineering, or a build you need help scoping. Include the stack, the timeline, and the problem you are trying to solve.
Corrections & feedback
Something in an article is wrong, out of date, or unclear. Send the URL and what tripped you up — these get fixed quickly.
Tool requests & bug reports
A utility behaving badly, or a repetitive task you wish had a tool. Browser and a sample input help enormously for bug reports.
Everything else
Questions about an approach, speaking and writing invitations, or simply saying that something here saved you an afternoon.
Working together
I take on a limited amount of consulting and contract work alongside full-time engineering. The engagements that tend to go well are ones where the problem is concrete and the scope is honest about its own uncertainty. Typical examples:
- A React or Next.js application that has grown past its original architecture and needs a rendering, routing, and state strategy that will hold for the next two years.
- A front end that is slow, where nobody is quite sure which of the plausible causes is the real one — usually a measurement problem before it is a code problem.
- A Node.js or TypeScript service that needs authentication, access control, background jobs, or a sane deployment story.
- A Generative AI feature that works in a demo and falls over in production — retrieval quality, prompt structure, evaluation, cost, and streaming UX.
- A design system or component library that several teams need to share without stepping on each other.
If that sounds like your situation, describe it in the form above along with your stack and rough timeline. If it is not a good fit, I will say so directly rather than waste your time — and where I can, I will point you at someone better suited.
What I do not respond to
To be upfront about it: unsolicited guest post offers, paid link or link-exchange requests, sponsored article proposals, SEO service pitches, and bulk outreach do not get a reply. Every article here is written by me, and no link on this site has ever been sold. Declaring that plainly saves us both some time.
Your privacy
The form collects your name, email address, and message — the minimum needed to write back — plus the answer to the arithmetic check, which is discarded immediately. Your details are never sold, shared with third parties, or added to a mailing list, and there is no newsletter to be signed up to without asking.
Full detail on what is stored and for how long is in the privacy policy, and cookie use is covered in the cookie policy. If you would like anything you have sent deleted, just ask and it will be.