Editorial ⊣ A note from the editor
After almost two hundred posts written under nine series labels, the labels are coming off. From tomorrow, this feed runs as a small editorial week instead. Four days, four ressorts, no series hooks, no episode counters, no content-marketing furniture.
Why now, what changes, what stays. With a tip of the hat to the readers who have sat through the old series and may, this evening, be wondering what just happened to the headers.
What Goes
The eight regular series I have been running here, all of them in earnest, all of them with their own conventions and their own audiences, are being retired in their published form.
Technical Beauty, with its thirty-seven episodes celebrating the tools we forgot we admired. The Unix Way, with its eighteen comparisons across the BSD and Linux divide. By Design, the architecture journal. In the Net, on vendor lock-in. Not in the Brief, on the things engineers absorb without being asked. On Second Thought, the Sunday slot for the routines we no longer examine. Tales from the Bare Metal, the post-mortem column. Bytes of Art, the small cultural sidelight. And The Invoice, on the slow ways money quietly rearranges engineering decisions.
None of those bodies of work go away. The archive stands. The pieces remain readable, the arguments are still on record, the work will not be deleted. But no new pieces are being written under those mastheads.
Why not. Two reasons.
The first is that the series-brand format, after some hundreds of posts, becomes a procrustean bed. Each post arrives pre-shaped by the masthead it is assigned to, by the conventions of its series, by the hook symbol that needs to be there because the hook symbol has always been there. The shape is doing some of the writing for me, and that is starting to flatten the work. Removing the labels removes that thumb on the scale.
The second is that the recurring readers I most respect on this platform, the ones who think for a living about systems, do not write under series labels themselves. They write essays. The day of the week, more than any brand, signals what kind of piece to expect. The shape of an editorial week, where each day belongs to one set of questions, suits the position the work has earned better than a publishing schedule of branded slots.
A reader might fairly point out that this transition, in itself, involves a fair amount of branding. New ressort names, new colour palette, a layout master, a typography discipline, four illustrative roles for the recurring figure. There is no honest way to deny the observation. Less labels would be a more accurate description than less branding. What goes is the series-as-product framing. What arrives is a quieter editorial framing in its place. The honest claim is that the new framing earns its keep by serving the work, and the old framing had begun to do the opposite.
What Stays
The voice. The British editorial tone, the British humour, the dry technical precision. The FreeBSD anchor wherever it earns its place. The honest disclaimers that say where the argument ends. The first comment on LinkedIn that links to the full piece on vivianvoss.net. The Sunday long-form discipline. The respect for readers across the BSD and Linux divide, especially when the licence argument cuts close to home.
Security gets its own fixed weekly slot. The interruptive Wire Fire sitrep, which fired on demand when a tier-one event crossed the threshold and which pre-empted the scheduled post on the days it spoke, has been retired in favour of a scheduled Friday column. The brief is the same: what moved during the week in our territories, what to know before the weekend. The cadence is calmer; the writing has time to settle; the readers know where to find it. The trade-off is honestly a trade: the interruptive format was sometimes the right shape for a fresh tier-one event in the first twenty-four hours, and that immediacy goes with it. The compensation is that the weekly reading habit, the one that the rest of the editorial week relies on, becomes the same habit that delivers the security briefing.
The New Shape
Four days, four ressorts. Each day belongs to one set of questions.
Monday: Unix Universe. FreeBSD engineering, BSD and Linux comparisons, the engineering tree that holds together as one coherent base system rather than as ten thousand independently governed upstream projects. Mondays are for working tools and the way a tradition that started in Murray Hill in the early seventies still pays off in production today.
Wednesday: Lean Software. Less code, less framework, less bloat. The discipline of subtraction in the stack. The five-kilobyte question for a typical single-page application. The build step you did not need. The microservice for a two-person team. The polyfill that outlived the browser it was written for. The cache as a reflex rather than as a decision.
Friday: Security Review. The week's vulnerabilities and vendor moves in the territories we actually work in, not the territories that make the largest noise on Bloomberg. BSD and Unix CVEs with real production reach. European vendor and governance shifts. Supply-chain compromises that matter to a working engineer. Not an alarm; a briefing, with a calm tone, on what to know before the weekend.
Sunday: IT Philosophy. The longer questions. Architecture as ethics. Ownership versus accessibility. Licence philosophy and the European software sovereignty question. AI provenance. Wabi-Sabi engineering. The single ressort where the broader analytical lens is welcome on the page and where each piece carries its own limit, written into the body, on where the argument ends.
Within each ressort, pieces will sometimes run as small bows of two or three over consecutive weeks, with a one-of-three or two-of-three marker on the cover. They will sometimes run as a single solo essay. They will occasionally take a Sunday-long-form turn into a fuller essay on the blog, with the LinkedIn piece running as the entry point. The format breathes within the week; it does not shape the work.
What That Means Tomorrow
Tomorrow opens the first bow on Sunday: the first of three pieces on European software sovereignty, under the title Open Is Not Owned. The piece asks the question the rest of the bow rests on, which is whether the licence of a piece of software is the question of who actually owns it, and what that distinction implies for any honest claim of digital independence. The second piece, the following Sunday, walks through the single coherent base system that makes ownership actually possible in practice, and the engineering case for it. The third piece, the Sunday after, names the layer of the stack that cannot be forked at all, regardless of licence, and what that means for any sovereignty claim that wants to be taken seriously by a working engineer.
A small editorial week begins. Same writer, four angles, sharper form. The hooks come off; the work does not.