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.
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.
Search screens that stay simple as the filters pile up: name what users can filter on once, and let the database do the work. Most APIs grow a tangle of optional parameters nobody tests instead.
A list screen users can bookmark, share and hit Back on without losing their filters, and that never shows an error over data that loaded fine. The rules behind it, and the Vue composables that apply them.
Answer 'everything under X' for category trees, org charts and folders, at any depth. Three approaches, from one that works on any database to one that scales to millions of rows, and how to pick.
Keep file storage behind one interface and let each environment choose disk, network share or Azure in configuration. Tests run without cloud credentials, and moving your files later is a copy job, not a rewrite. Uploads are typed by the server, so none can pose as a page of your site.
One table for every customer, supplier and employee, with roles and alliances as dated relationships instead of extra tables. Tested on Westeros, where everyone knows who betrayed whom and when.
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.
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.