A note on technical writing
So I wrote stories and weird book reviews instead, but ignoring technical writing was foolish because documenting a specific problem (such as a demo for inline SVG sprites) requires a completely different set of skills from fiction or think-piece writing.You have to draw a line at one point or another around your audience and their technical prowess. Do you have to explain how inline images work? Or the peculiarities of the DOM ? Where do you begin? Is it patronising for the majority of readers if you take the easy way out and explain a concept with jQuery? Or is it instead insulting if you disregard the troubles that less experienced folks might experience with this example?
The trouble is this: to write some CSS you must first invent the universe.
Besides that I’ve been working on a redesign of my personal website and so I’ve spent a lot of time thinking about what I want from it in the coming years. First I’m thinking about basic UX and organization (I love the idea of URL-first design) and I want to write a lot more fiction so the site will need to compensate for that. Afterwards I’ll move onto basic performance improvements, switching hosts and, of course, typesetting.
The impetus for setting typographic details should always start from a reading of the text, hence my return to older posts in order to see how my writing style has changed over time. By next week I’ll have a general typographic system that I’ll dig into a little bit and show what I’m thinking about.
Behold! My newsletter—sent infrequently—about new things that I’m working on. Every so often it’ll contain notes about web design and publishing things that I’m interested in, too.