I sat down this week to add a fourth social account to the site and realised, somewhere in the middle of it, how little of the last few days had been about wizardry at all. What I had been doing instead was learning four unrelated crafts, badly, in public. It seemed worth telling you about, partly because it is what has actually been happening, and partly because I think it illustrates the argument better than anything I could write on purpose.
Where things are
Running a mailing list is a craft, and I did not have it. This letter is the second. The first one went out looking wrong — a box drawn inside another box, the title printed twice, and a heading proudly announcing itself as “My Awesome Newsletter”, which was the default I had not noticed. Nothing was broken and everybody was very kind about it. The thing I did not know was that email has almost no layout: the tools the rest of the web uses simply do not work there, and the design has to be rebuilt in an older, cruder way that has not really changed since the nineties. I now know that. It cost one letter to find out.
Worse, and more interesting: the list has a spam filter that judges whoever sends the request, not the person signing up. It turned away two real people who had done nothing wrong, and told me in language that sounded like it was describing them. It was describing me. Two people nearly lost to a misread error message is the sort of thing you only learn by losing them.
Four social accounts is not four times one account. There are now four, and the rule I settled on early is that a piece gets one line, written once, that has to work on all of them. Not four tuned variants — those would be four things to keep in step, and three of them would quietly rot. That decision has survived contact with a fourth platform without needing a word changed, which is the only real test of a rule.
What I underestimated was the maintenance. One of the four hands out a key that stops working after sixty days, and does it silently: nothing announces itself, posting simply stops. There is now a reminder in my calendar, which is a very unglamorous solution and the correct one.
I also managed, in one afternoon, to post fifteen things across three accounts in about ninety seconds while clearing a backlog. It reads exactly like a bot. Nobody had built anything to slow it down because until that day there had never been more than one thing waiting.
Being findable is a different skill from being good. The phrase “modern wizardry” already belongs to an older spiritual organisation, and to several accounts and pages that have held those words for years. None of that is a dispute — they were there first — but it does mean a search engine has no particular reason to think this is a distinct thing rather than more of theirs. Most of the least visible work this week has gone on that: proving, in ways a machine can check, that this domain and these accounts are one organisation and not another. Some of it is genuinely elegant. Most of it is fiddly.
And the part that is not technical at all. The most useful thing anyone has done for this project so far was reply to the first letter with a question. That question became the whole of Dispatch 001. The answers people wrote in the box on the signup form have been better than anything I arrived at alone, and I have changed my mind about at least two things because of them. I had assumed the hard part of a small community would be attracting people. It is not. It is asking questions specific enough to be worth answering.
Something to argue with
The Value of Knowing What You Don’t Know
Admitting ignorance is treated as a weakness in most professional settings. It is in fact the most reliable instrument any of us have.
What I think is weakest about it, now, is that it describes the map as though you can consult it. You cannot, not really. I did not know that email had no layout; I could not have known, because that particular gap had no shape until I walked into it. The essay makes knowing your own ignorance sound like an inventory you keep. In practice it is more like a wall you find in the dark, and the only way the map improves is by barking your shins on things.
So, one question, and I would genuinely like an answer:
When did you last find the edge of what you knew by walking straight into it?
Reply and tell me. A sentence is plenty.
The method eating its own cooking
Here is the part that is only in this letter.
This project argues that breadth is worth having, that the interesting things happen where disciplines meet, and that being the least qualified person in the room is a normal cost of learning rather than a humiliation to be avoided. It would be a bit rich to argue all that and then only ever build things I already knew how to build.
I did not plan this as a demonstration. But four days spent on email, social platforms, search and asking better questions — four things, none of which is the subject, none of which I was any good at — is a more convincing account of the method than an essay about it would have been. Every one of them went wrong before it went right. That is not a caveat to the story; it is the mechanism. You do not get a map of your own ignorance by reflecting carefully. You get it by trying something and being wrong in a specific, embarrassing, informative way.
One thing I want to be accurate about, because this genre invites exaggeration in both directions. None of it was hard. It was new, which is a different thing, and the two get conflated so routinely that I think the conflation does real damage. Unfamiliarity has a particular texture — the slight resistance of not yet knowing where anything is — and people read that texture as evidence they are out of their depth, when it is only evidence that they have not done this before.
Being a beginner four times in four days was not unpleasant. It was mostly just novel, and occasionally slow. If more people knew the difference, I suspect rather more of them would be four things into a week they had not planned.
Reply to this one; it comes straight to me.