The source code for SimCity Local Code was Sorkin’s attempt to design a whole city from scratch—with one big twist. The whole thing had been written as if it were the byzantine, nearly impossible to follow codes and regulations for an entire, hypothetical metropolis. The effect is like stumbling upon the source code for SimCity. Sorkin’s exhaustively made point was that, if you know everything about a given metropolis, from its plumbing standards to its parking requirements, its sewer capacity to the borders of its school districts, then you could more or less accurately imagine the future form of that city from the ground up. Geoff Manaugh, A Burglar's Guide to the City Local Code: The Constitution of a City at 42º N Latitude rulesregulations
Politics and the English Language An Essay by George Orwell jarango.com Never use a metaphor, simile or other figure of speech which you are used to seeing in print. Never use a long word where a short one will do. If it is possible to cut a word out, always cut it out. Never use the passive where you can use the active. Never use a foreign phrase, a scientific word or a jargon word if you can think of an everyday English equivalent. Break any of these rules sooner than say anything outright barbarous. ruleswriting
Blogging with Version Control An Article by Will Darwin willdarwin.com I’ve been musing for a while now on the way blog posts are typically presented—in reverse chronological order. This format has never truly made sense and does not reflect the way good writing and thinking happens. ...The main issue with the ‘pile’ system is that this post is eventually buried beneath more recent pieces of writing; there is no incentive for revisiting or updating the work. Even worse, if an author does decide to unearth the piece and make some major changes, those who read the original piece are not made aware of these alterations. The sorting order is static. bloggingwritinginformation