Patterns, gotchas and small wins from fifteen-odd years of .NET and web work — the Regira packages and modules, entity pipelines, editorial front-ends and everything between.
When two people save the same record, the second save is refused instead of quietly erasing the first, whichever database the application runs on. The second user reloads and re-applies their change.
When an agent builds the app, a framework that owns the plumbing shrinks the review to the part that is your business. What to read first: which questions the API answers, what a save may change, and which rules run every time.
Saving a record from a small form should never wipe the items attached to it, while the full edit screen can still remove them all. How an API tells an omitted list from an empty one, and what a form sends for a row the user removed.
A coding agent built working apps on a framework it had never seen, without inventing a single method. The reason is documentation that lives with the code, is served one piece at a time, and tells the agent what to do next and how to check it worked.
Before an agent builds a bigger app, sort each request into what the framework provides, what the agent must assemble, and what is missing. A plan for a shopping-list app with sign-in, sharing, photos and offline use, and what changes when an app keeps growing after its first run.
Hand a coding agent a six-line brief and get a running .NET and Vue app, with sample data and a clickable UI, in about half an hour. Step by step, with no license and no account.
Copy-paste settings that connect Claude, OpenAI Codex, Gemini, GitHub Copilot or Cursor to the Regira documentation server. Plus what changes on an existing application, past the free tier, and without a network.
Know how many people read your site and where they come from, without a third-party script, a cookie or a consent banner. What the blog you are reading records, what it cannot, and how crawlers are kept out of the count.
Keep an update from blanking a field the form never showed, such as a reference code, a close date or a total. What causes it, why every line involved passes review, and the one-line declaration that prevents it.
One place for each rule a save must obey, so it holds whether a user, an import or a nightly job did the saving. Required fields, timestamps and a code that never changes stop being scattered across controllers.
One customer must never see another's rows, in any list, count or endpoint, including the one added next year. Seven requirements that make that a property of the system, and which of them no library can meet for you.
Let users ask for this or that, one brand or anything overdue, in a list that still pages and sorts like every other. How to offer 'or' without a flag nobody trusts.