Editorial policy

The Augmented Dev is a personal technical blog written and published by Rishi Verma. This page explains how posts are chosen, how they are produced, and what happens when something is wrong.

What this site is for

The blog exists to write down field notes that I wish had existed when I was stuck: Dynamics 365 and Power Platform behavior that is easy to misread, system-design tradeoffs, AI agents in production, DevOps habits, and a small set of interview-pattern write-ups. The aim is usefulness, not volume.

Who writes

Every published post is written or substantially edited by me, and I take responsibility for what it says. There is no guest-post program, no paid placement, and no affiliate relationship that changes a recommendation. When I mention a product, it is because I have used it or because it is the documented option for the problem under discussion.

How posts are produced

Some posts start as notes from a bug I just fixed. Others start as an outline I want to think through. For longer pieces I sometimes use Claude as a drafting assistant — to propose a section order, to suggest an example I might have missed, or to help me rewrite a muddy paragraph. I then edit the draft against primary docs, my own notes, and (where I can run it) working code.

A first draft from a model is not a finished post. I do not publish raw model output. Technical claims, code samples, and recommendations are ones I am willing to stand behind. If I cannot verify a specific version number, API name, or benchmark, I leave it out or say that I have not verified it.

This matches Google's public guidance on AI-assisted content: assistance is fine; unreviewed mass production is not. A scheduled generator used to exist in this repository. It is no longer on a cron. New posts go up when I have something worth publishing, not because a calendar fired.

What gets published — and what does not

• A post has to add something a search result or the official docs do not already make obvious: a failure mode, a tradeoff, a worked example, or a correction to a common myth.
• Thin notes, near-duplicates, and pieces I cannot stand behind stay unpublished. Unpublished drafts remain in the repository with a draft: true flag and are not listed, sitemapped, or served as public pages.
• Release-wave recaps and product-announcement summaries are not a regular format here. If a shipping change matters, I write about the operational consequence, not the marketing list.

Corrections

If you find an error — a wrong API name, a bad default, a sample that does not compile — please tell me. I correct the post, set or update the "Updated" date, and credit the reporter when they want to be named. I do not silently rewrite history to hide a mistake.

Independence

The site is not affiliated with Microsoft, Anthropic, Vercel, Google, or any other company mentioned in the posts. Views are mine. Advertising, when enabled, is labeled as advertising and does not change editorial choices. See the Privacy Policy for how ads and analytics work, and the Terms for the disclaimer that this is not professional advice for your specific system.

Comments

Comments are welcome when they add a correction, a counter-example, or a question. Spam, promotional dumps, and personal attacks are removed. The comment form is not a support desk for production outages.