Read a series

Building apps with an AI agent

A coding agent, a documentation server and a shopping list: a working app from a short brief, why the agent never guesses, and what happens when the brief grows.

1. From Six Lines to a Working Full-Stack App
2. Stop the Agent from Guessing
3. What Happens When a Simple App Brief Gets Complicated?
4. Reviewing an App You Didn't Write

Filtering in Regira Entities

Six short parts on the read side of an API: naming what users can filter on once, then sorting and paging, the rules every query obeys, archiving, free-text search, and combining searches. Each part has a sample to curl along.

1. From Query Parameters to a Composable Filter Pipeline
2. Sorting and Paging Without Surprises
3. Filters You Register Once and Cannot Forget
4. Delete Without Losing Anything
5. A Search Box That Finds Café When You Type Cafe
6. Let Users Search for This or That

Writing in Regira Entities

The write side of the same API: where the rules that hold on every save belong, the two silent traps of a PUT and a DELETE, and what sending a child list to the API really means.

1. Save Consistently from Every Screen and Job
2. Validation in One Place
3. An Update That Blanks a Field the Form Never Showed
4. Omitted Is Not Empty
5. When Two People Edit the Same Record
6. Send the Mail Only When the Order Is Really Saved

Entities front-end

Building the list and edit screens over a Regira Entities API in Vue 3: what the API must expose, and what the client composables do with it.

1. List Screens That Survive the Back Button
2. Edit Forms That Survive Reality
3. Saving, Saved or Failed

File storage behind one interface

Files behind one interface: test on disk and ship to the cloud by configuration, then a small tool that copies between disk, a network share and Azure from one config file.

1. Test on Disk, Ship to the Cloud
2. Copy Files Between Disk, Network Share and Cloud

Hierarchical data

Trees in a database and on a screen: from a flat list with parent ids to a tree in one line, hierarchies at any depth in EF Core, and the same tree in a Vue SPA, expandable and draggable.

1. From a Flat List to a Tree in One Line of C#
2. How to Query Hierarchies at Any Depth with EF Core
3. The API Sends a List, the Screen Needs a Tree

People, organisations and alliances

One table for every customer, supplier and employee, with roles and alliances stored as dated relationships instead of extra tables — and the realm on any past date as a single query. Westeros supplies the test data.

1. Westeros, the Iron Throne, and a Model for Complex Relationships
2. The Realm at Any Date