Notes from the field

About the author

I'm Rishi Verma, a developer. This site is where I write down problems I have hit, patterns I have shipped or audited, and the explanations I wish had existed when I was searching for them. I am not writing as a spokesperson for any employer or vendor.

The topics I keep coming back to — because they are the ones I spend time in — are:

• Dynamics 365— Finance & Operations (X++, batch jobs, data entities, dual-write), Customer Service, Sales, and Copilot integrations.
• Power Platform — Power Automate cloud flows, canvas and model-driven Power Apps, Dataverse, and ALM with solutions and pipelines.
• System design — caches, queues, idempotency, consistency, and the tradeoffs that show up in both production systems and interviews.
• AI agents — tool use, MCP, evals, and keeping a model from skipping the check the workflow depends on.
• DevOps and the modern web — pipelines, PowerShell, Next.js, React, TypeScript, and the operational habits that keep software shipping.
• Interview prep — a curated set of pattern write-ups in Python, not a dump of every LeetCode prompt.

You can find me elsewhere here:

• X (Twitter): @merishiverma
• GitHub: rishi1212
• LinkedIn: rishiverma12

Why this blog exists

Official docs tell you what a feature is for. They rarely tell you which default will bite you on the first production Friday, or which two Microsoft products share a name and not a behavior. I started writing so I would not have to re-learn the same lesson six months later, and so the next person searching the same error has a path that is more than a forum thread from 2018.

The voice I aim for is direct: what broke, what I tried, what I would do again, and what I would not. If a post recommends an approach, I have either used it or I have watched the alternative fail. I do not invent benchmarks, quotes, or product capabilities to make a section look finished.

How posts are written

Most posts start as notes from a real problem. For some longer guides I use Claude as a drafting assistant — outlining, suggesting examples, catching cases I missed. Every post is edited and signed off by me before it is public. The editorial policy has the full version of that process, including how corrections work.

Code samples are tested where I have an environment that can run them. Where they target a specific tenant or a build I cannot reproduce locally, I say so. If you spot something wrong, tell me — I update the post and keep the published date honest.

What this blog isn't

• It is not affiliated with Microsoft, Anthropic, Vercel, Google, or any other company mentioned.
• It is not sponsored. Posts are not paid placements.
• It is not advice for your specific production system. Validate before you ship.

Get in touch

The working way to reach me is the contact form. I also read comments on posts. I reply when I can; I read everything.