Skip to main content

24 posts tagged with "tooling"

View All Tags

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.

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.

Jev, Sorted: What TypeSafe's 'System One' Model Actually Is, and What Is Still Just a Claim

· 18 min read
Pere Pages
Software Engineer
A sorting machine on a factory line: parcels arrive on a conveyor belt and a single mechanical arm flicks each one into one of several labelled chutes without pausing, while a slower human clerk at a desk in the background writes a full report about a single parcel.

TypeSafe AI launched Jev on 15 September 2026 with a headline of "193.6x faster, 444.6x cheaper" and a promise that it "can't hallucinate". Read the primary sources rather than the reposts and a narrower, more interesting product appears: a frontier-trained classifier for software, not a better large language model, with every number so far reported by the vendor.

Resuming Claude Code Sessions Properly: What Comes Back and What Doesn't

· 12 min read
Pere Pages
Software Engineer
A person at a terminal desk picking up one of several luminous threads that trail from the keyboard back into a dark archive of drawers; the chosen thread glows brighter than the others, and a paper notebook lies open beside the keyboard

I opened Claude Code on a side project after a day away, and it greeted me with a careful reconstruction of what we had been doing, pieced together from the notes file and the working tree. It was right, but it was a guess. The whole conversation that produced that work was sitting on disk, one command away. Here is how sessions actually persist, what a resumed one gives you back, and what it never will.