Notes · Journal ·
Logbook 2026-11-16
Tonight I finished the second draft of my first essay, five days after I started it.
It’s on design and the repository. It follows the writing-prep skill I set up on 3 November, but this time the process ran well beyond a brief and a draft. Here are the steps, as they came.
The initial substance.
My notes of 12 November, some first thoughts and a conversation with designers at work, sorted into the five steps of a brief.
The angle.
Questioned in rounds, along with the point of view and the aim. A first set of 18 questions grew to 24 over the days: on my position, what I know first-hand, the strongest objections to it and what it would cost, the reader, and the form. Even a single word of the title got a question of its own.
The brief.
Revised after my review on 14 November, then again with my answers on the morning of the 15th.
The outline.
A plan where each section answers one question, with four candidate sentences to keep.
The first draft.
Written on the afternoon of the 15th: about 3,500 words and 34 footnotes, well over the 2,000 to 2,500 the outline aimed for.
The draft check.
The draft read against the brief and VOICE.md: five passages the brief doesn’t support, and four lines that come close to what I said I refuse to say.
A voice revision.
This evening. Reading the first draft, I saw it gave my thoughts in the order I had them: each point of the outline had become a paragraph, and the reasoning that joined them had stayed in the brief. I added a section for long reads to VOICE.md, tried it on one section, then rewrote the whole draft. What changed:
- each section opens by placing the reader, and closes on what it settled or on the question the next one takes up;
- each paragraph opens on how it follows from the one before, instead of a “then”, an “also” or a “too”;
- the terms of one profession are defined for the other the first time they appear;
- every source is introduced before I quote it;
- one image comes back through the piece, instead of a new one in each section.
The links cost words: the second draft runs to about 4,700. That’s the price of being understood.
The next steps.
My review of the second draft, and my answers to the questions the draft check left me.
What I enjoyed most was throwing ideas out one after another and watching them connect. On the 12th they came all day, and each one found its place in the brief, the research and the plan. A thought about versioning came on the evening of the 14th, after the brief and the plan were written. It felt like magic to see it slot in so easily and naturally. It came back with why it mattered to the essay and where it belonged in what was already there: one point of the thesis, an echo in the prerequisites, and an aside on the canvas.
The other satisfaction was testing my ideas against my personal knowledge base, edkb. Seven of its notes already touched the subject and led to their public sources. Some confirmed what I thought, others complicated it, and one warned me not to imply that the developer’s craft was ever easy. On the 15th, before drafting, I asked for one more pass over edkb’s latest review and the 21 feeds I’m adding to it: 226 items, eight sources kept. My ideas came out of it consolidated, and the essay sourced, more solid than my opinion alone.
It takes time. Five days so far, and the essay isn’t online yet. But the effort doesn’t feel the same. I guide the AI around my ideas to shape the path my thinking takes, and it helps me cross them with my sources and put them into form. The substance and the original angle stay mine.
I’m not an author, and choosing the right words isn’t my job. What I want is to share my ideas clearly, and to make my thinking legible. With this process, I can focus on where I want to bring my value.