Last week, the Editorially team announced that they were closing up shop and began the process of an orderly shut-down. The loss has been difficult primarily because I loved the tool and the team, and I thought they deserved to succeed. I still think that, and I’m going to be sad for a long time, and I may eventually write more about why. But today I’m going to be selfish instead, because the secondary reason I took this loss hard is that Editorially had become indispensable to my work. Losing it feels like losing a cherished and necessary robot-arm.
Editorial work—reading, drafting, revising, reviewing, line-editing, copyediting, marking up, illustrating, and publishing—is what I do for a living. It’s also a good chunk of what I do for love. And like a programmer with very specific requirements for their dev environment, I care a lot about the details of my editorial tools: how they work, what they allow, how they look, how trustworthy they seem. Read more ⇒