Hiatus
I’ve been blogging regularly since 01 August 2006: every day for that first year, five times per week for four years after that, and at least once per week since 01 August 2011. Now it’s time for a break.
[more...]
I’ve been blogging regularly since 01 August 2006: every day for that first year, five times per week for four years after that, and at least once per week since 01 August 2011. Now it’s time for a break.
[more...]
I’ve grown increasingly unhappy with WordPress, despite the fact that it’s served me fairly faithfully for over seven years. The main reason is performance—this blog is now just too slow to load. There are definitely things I could do to tackle that, but having to do so is a sign that it’s not the right platform. The other reason is philosophical—I no longer think that a web application backed by a database is the best approach for a blog.
I’ve been thinking about writing my own—of course[1]. So first I should establish the requirements.
[more...]
I switched to writing in reStructuredText in mid-2009, and to writing in Vim in early 2010. Since then I’ve made a lot of tweaks to improve editing efficiency, and eventually collected these in a Vim plugin (and a Python script). The following discussion of that plugin might be of interest to anyone concerned with writing efficiency and/or editor customization.
[more...]
I use plain text formats for all of my writing, and you should at least consider doing the same.
By “plain text” I mean not only a text (as opposed to binary) file format, but also something that is plainly readable when simply listing the contents of the file—that is, a format you don’t necessarily need a specific tool to read. Such formats are more flexible, more robust, more malleable, and more future-proof than more complicated alternatives.
[more...]
A discussion of common and custom blog features, and candidate applications that might provide them.
[more...]
I’ve mentioned pandoc once before, and it’s again proved rather useful. I’ve been looking for more ways to use it, as I love its core principle (although I naturally wish that it focused on reStructuredText rather than Markdown) of being a comprehensive text format converter. It might at one point be the answer for getting from reST to PDF—something that the current reST tools don’t help me with because I insist on using Unicode, and XeTeX isn’t yet supported. But today pandoc helped with a different task: going from reST to plain text.
[more...]
After a highly enjoyable, productive, and extended period, it’s time for me to return to the world of paid work.
I’m quite happy with the things I’ve done during my time off. Many of them are important only to me, but then, it’s been my time off.
[more...]
The New York Museum of Modern Art has added the @ symbol to its architecture and design collection. Originating perhaps as a Latin abbreviation for “toward”, it showed up on one of the early Underwood typewriters (possibly the Underwood 1; it was definitely on the Underwood No. 5) and was used for “at the rate of”, which usage still survives.
[more...]
I had eight goals for 2009, and all of them that I’m going to get done I’ve already completed. Time to review.
[more...]
It took me a while to get there, but I now have a working toolchain to automate going from an RTF file (or a Word document) to reStructuredText. The final link took the longest to find, and turned out to have been right there all along (no, I’m not going to turn this into a retelling of The Alchemist). But if you’re interested in how to get from Word to a sane format (like reStructuredText), this post will interest you.
[more...]
Last week I posted about my setup for going from reStructuredText to WordPress. It involved a shell script, some Python scripts, and the pbpaste and pbcopy commands. It worked, but it was a little on the convoluted side.
Now I have a slightly better process, and one that I will have used to publish this post.
[more...]
I wrote about moving my writing over to reStructuredText on Sunday, and since then I’ve moved both my morning pages and my blog writing to it. The latter proved more complicated, primarily because I wanted to make the process almost as easy as writing pseudo-HTML (which is more or less WordPress’ native format, and kind of mine, too, for the last several years). With some hacky wrangling, I’ve managed to set that up.
[more...]
I’ve written before about my wish for semantic word processing tools, and two years on I still haven’t found something that suits me. I think that WYMeditor has definite promise, but unfortunately the authors are aiming that at browser-to-server functionality, rather than in-browser standalone functionality. This isn’t such a major obstacle for me, but it is one of the reasons why I’m hesitant to move over to using a project that hasn’t reached version 0.5 yet.
[more...]
I already have a buch of plans for larger projects, including finishing the sfmagic.org rewrite, but I think it makes sense to have some smaller projects to work on as well, things that I can switch to and make significant progress on in a relatively short amount of time.
[more...]
A colleague gave a presentation at work today on Pylons, a web framework for python. I was curious about the slides he was using, because they looked like they could be in S5, which I like. So afterwards I asked him, and he said that he wrote them in “rest”, which confused me at first because I thought of the REST approach to Web architecture. He was in fact talking about reStructuredText, a plaintext markup system that I’d never encountered before.
[more...]