About Amit Verma

I am Amit Verma, a senior full-stack engineer with more than twelve years of professional experience building web products for banking, insurance, blockchain, and media companies. I work primarily with React, Next.js, Node.js, and TypeScript, and over the last few years I have spent an increasing amount of my time on applied Generative AI — retrieval pipelines, agent tooling, and the interface design problems that come with streaming model output.

Most recently I spent four years at NeoSOFT Technologies as a Senior Full-Stack Engineer and Team Lead, where I led a cross-functional group of 25 to 30 engineers and delivered six enterprise client portals. That work included a secure back-office platform for BDO Unibank, one of the largest banks in the Philippines, an insurance platform for Zurich Kotak, blockchain provenance products with Everledger and e-Procure, and the OTTplay streaming service. Before that I worked as a senior engineer at Webcontxt and Startbit, and started out in 2014 building client websites at Michrons Technology.

The through-line across all of it is unglamorous: shipping software that other people depend on, on a deadline, with a team. That is the perspective I write from.

tayloramitverma.com is my personal engineering site. It exists for two reasons, and everything on it serves one of them.

The first is writing. When I solve a problem at work that took real effort — a Next.js image pipeline that designers would actually trust, background jobs in Node with BullMQ, TypeScript generics for UI components, building MCP servers, or getting a RAG system to behave — I write it up properly. Not a summary of the documentation, which you can already read, but the decisions, the trade-offs, and the parts that broke. Each article includes working code, and I state the versions I tested against so you can tell whether it still applies.

The second is tools. Over the years I kept re-opening the same handful of utilities: something to decode a cron expression, something to sanity-check a regular expression, something to turn a JSON response into TypeScript interfaces. Most of what I found was slow, covered in ads, or wanted an account. So I built my own and put them here, free and without sign-up. The regex, cron, and JSON tools, the code playground, and the calculators all run in your browser; the data you paste into them generally never leaves your device.

I would rather publish one article that is genuinely useful than ten that restate a README. A few commitments follow from that, and they are worth stating plainly because a lot of technical content on the web does not honour them.

Everything here is original

Every article, guide, and tool on this domain is written and built by me. Nothing is scraped, spun, syndicated, or generated wholesale by a language model and posted unread. I use AI tooling the way most engineers now do — as an assistant while drafting and while writing code — but the structure, the technical judgement, the testing, and the final text are mine, and I am accountable for them.

Code is run before it is published

Snippets in an article are taken from something that actually executed. Where a result depends on a library version or a runtime, the article says which one. This is the single biggest difference between a tutorial that works and one that wastes an afternoon.

Corrections are made openly

Software moves, and articles go stale. When a reader points out an error, or an upstream change invalidates an approach, I update the article and its modified date rather than quietly deleting the page. If you find something wrong, please tell me — it is genuinely helpful.

Independence

I am not paid by any of the vendors, frameworks, or cloud providers I write about. When I recommend a tool it is because I used it and it worked; when I criticise one it is for the same reason. Any situation where that is not true would be disclosed in the article itself and is covered in the disclaimer.

This is a personal site, not a business, and it is funded by me. It may display third-party advertising to offset hosting costs. Advertising never influences editorial content: advertisers have no input into what I write, no review of articles before publication, and no way to have criticism removed.

The tools collect nothing beyond what they need to run, and most of them run entirely client-side. What is collected, why, and how to opt out is set out in full in the privacy policy and the cookie policy.

• Articles — long-form guides on React, Next.js, Node.js, Python, and Generative AI.
• Developer tools — free regex, cron, and JSON to TypeScript utilities that run in your browser.
• Code playground — a zero-setup HTML, CSS, and JavaScript scratchpad built on the Monaco editor.
• Calculators — compound growth and scientific calculators with the maths explained.
• Résumé — the full professional history, projects, and technical skills.

I am always happy to hear from readers — about an article that helped, one that has an error, a tool you would like to see built, or a project you think I would be a good fit for. The fastest route is the contact form, and I answer most messages within two business days.