Skip to main content

Ontologies and Domain-Driven Design: What's New, What Isn't, and Why AI Cares

· 14 min read
Pere Pages
Software Engineer
A flat illustration: on the left, a network of blue dots joined by thin lines; on the right, solid teal and amber blocks with gears and a padlock; in the middle, a small robot stands on a bridge between the two and presses a panel of buttons

Ontologies are popular again, mostly because of artificial intelligence (AI) agents. A developer who knows Domain-Driven Design will find much of the idea familiar. This post covers what the two share, where they differ, and why the interesting work now is letting AI programs use your existing business model safely.

Why Anthropic Replaced Git with Scion, and What the Rest of Us Can Learn

· 16 min read
Pere Pages
Software Engineer
A flat illustration in two halves: on the left, a twisting tree whose branches each end in a heavy box, with a full copy going to every laptop in a row below; on the right, one glowing central server surrounded by small robots, each linked to it by a thin line and receiving a single page

In 2026, Anthropic's artificial intelligence (AI) agents began to merge more than 30,000 code changes a day into one repository, and git could no longer keep up. So Anthropic built its own source control system, Scion. Here is the problem it solves, how it works, and what it means for teams that will keep using git.

Claude Code Worktrees: Where They Live, How They Work and How to Use Them Well

· 14 min read
Pere Pages
Software Engineer
A flat illustration of one tree trunk splitting into three branches, each holding its own lit desk with a laptop: robot assistants work at two desks and a person at the third, and thin lines run from every desk back to a shared archive of drawers at the roots

Two Claude Code sessions in the same folder will sooner or later edit the same file and undo each other's work. A worktree fixes that by giving each session its own copy of the files on its own branch. Here is where Claude Code stores worktrees, how they work, what they share with your main folder, and the small routine that makes them worth using.

Sandboxing Agent Graphs in Claude: Where Each Agent Runs and What It Can Reach

· 22 min read
Pere Pages
Software Engineer
Seven small robots work at desks on a dark blue background. Six of them sit inside glass cubes and one does not. Glowing lines carry small notes between them, and the lines that lead away from the group end at closed gates on both sides.

When many Claude agents work together, a single agent that is tricked by hidden instructions can pass those instructions on to all the others. This post explains what a sandbox protects in a group of agents, which kinds of isolation exist from a simple command filter to a separate virtual machine, how to configure them in Claude Code, and which setups work well in practice.

What it really takes to run AI on your own files: models, memory and search

· 29 min read
Pere Pages
Software Engineer
An open laptop on a wooden desk at dusk, with a small library of books, folders and code files rising from its screen under a glass dome; a thin lime-green thread of light runs from a highlighted page to a glowing chip beside the laptop, while clouds drift past outside the dome

A laptop with 16–32 GB of memory can answer questions about your own notes, code and unfinished ideas, and none of your data leaves the computer. Choosing the model is the easy part. Two other things decide whether the answers are useful: how much memory the model has, and how well it finds the right pages of your files. Without them, it just guesses, and it sounds sure even when it is wrong.

Who Owns Your Code's Home? GitHub, GitLab and the Forge Landscape

· 20 min read
Pere Pages
Software Engineer
A stone blacksmith's forge at dusk: inside, a smith hammers a glowing graph of branching commit nodes on the anvil, blank ownership signs hang above the door, and a lone figure walks away down the road carrying only a small lantern

Nearly every software company keeps its most valuable asset on a platform somebody else owns: GitHub, GitLab, Bitbucket, or one of a handful of smaller hosts. Your git history can leave any of them in an afternoon — almost nothing else you built there can, so who owns the platform matters more than its feature list.