The letter

One letter a week, starting soon.

The week's signal, what shipped, what is worth running tonight, and the editor's note. No tracking, no ads, nothing else.

We keep your address, your language and the date you joined, nothing else. Every letter has a one-click unsubscribe link that deletes the record.

← Accept All   Editor’s notes
Editor’s note

A Repository's Folders Decide Who Gets Believed

2026.10.31Yuki Halvorsen

I cloned a new repository at midnight for no better reason than curiosity, and before I had read a single line of code the directory names had already told me who gets trusted and who gets watched. Three layers, one repo is the plainest description I have seen all year of what most engineering teams actually believe about their own code, once the slide decks are put away.

The structure is almost embarrassingly simple: core/, plugins/, contrib/. Core is the part a maintainer will stake their name on — tested, reviewed, versioned, the thing you can build a product on without reading the diff first. Plugins sit one step out: useful, swappable, reviewed but not guaranteed forever, the way a good extension should be. Contrib is the lost-and-found, the drawer nobody sorts. Nobody promises contrib will still work next Tuesday, and the repository says so in the one language a terminal cannot misread: a folder name.

What I like about this is not the organisation, which any team could sketch on a whiteboard in five minutes between meetings. It is the honesty of putting the gradient of trust into the filesystem itself, instead of a paragraph in a CONTRIBUTING.md that nobody opens before they copy-paste. A pull request into core needs tests and an owner's review. A pull request into contrib needs, roughly, that it runs once on the author's own machine. That single difference in gatekeeping is the real documentation, and it costs nothing to maintain.

This is the same decision I make every night at a smaller scale, shipping something before bed. The thing I am willing to put my name on tonight lives in one folder; the thing I am only willing to say 'this worked for me, try it' about lives in another, further from the door. A repository with three honest folders is just a team admitting, in public, that not every idea deserves the same promise, or the same reader.

I went looking in contrib first, the way you check a city's backstreets before its boulevards, and found a notebook whose only comment, in English, badly punctuated, read: works for me, no promises. It is the most honest changelog I have read all year, sitting quietly in the one folder built to expect nothing from it.

On the wire this week

  1. Three layers, one repo: a tour of google/adk-recipes Google Developers Blog

Yuki Halvorsen was born in Sapporo to a Norwegian father and a Japanese mother, wrote her first program on a school computer that took ten seconds to draw a circle, and spent eight years as an engineer in Stockholm before Tokyo pulled her back. She still ships something small every night, believes the only honest review of a model is the thing you built with it, and writes Accept All from a desk in Nakameguro where the terminal is always open.