RUGet in touch
WebsitesSystemsWorkNotesAbout
Notes

Write-ups, not articles

Each note is the long version of the "why this way" section from a case study. The case gives three paragraphs; the note gives the full account, with code and configuration.

27 September 2026Finding ancestors in handwritten registers: what AI does and where it goes wrongNotes from two family trees: where the records are, why search won’t find them, which techniques work with pre-1918 registers, where AI goes wrong and which rules stop it from writing your family history for you.

In the queue

  1. 01Workflows in YAML: when configuration beats codeFrom the case study: Freight accounting system
  2. 02One frontend, two portals: configuration from the backend instead of a forkFrom the case study: Client area
  3. 03Schema instead of code: JSON Schema as a way to keep configuration from falling apartFrom the case study: Low-code platform
  4. 04A React widget inside WordPress: why a separate repositoryFrom the case study: Shipping calculator
  5. 0534 ACF blocks: handing page assembly to a content managerFrom the case study: Page builder