Skip to main content

On Writing Well

I like doing things that have a body of theory behind them. For example, I prefer taijiquan to kickboxing, as a martial art, as it has deeper theory. So when I started blogging, I went looking for its theoretical foundations. I found them in the principles of good nonfiction writing. I bought two books: The Elements of Style, by William Strunk Jr. and E. B. White, and On Writing Well, by William Zinsser.

The book is unusual for a writing guide. Firstly, it is a good read. It is actually hard to put down. Advice on writing is given clearly and simply. That is part of it. However, Mr. Zinsser illustrates his points with personal anecdotes, and this is what makes the book so interesting. In the chapter entitled A Writer's Decisions, for example, he uses an account of a trip he took to Timbuktu. He walks us through the article he wrote, paragraph by paragraph, explaining what he wrote and what he was thinking at the time. Between the travel piece and its explanation, you get an idea of the author's personality. He's interesting. It makes his book interesting.

He is passionate about the craft of writing, and that comes through in a few humorous digs at bad writing. For example:

He or she may think "sanguine" and "sanguinary" mean the same thing, but the difference is a bloody big one.

Humour livens up the advice too:

Don't get caught holding a bag full of abstract nouns. You'll sink to the bottom of the lake and never be seen again.

Secondly, the book covers more than just grammar and rules for composition. It covers the whole craft of writing nonfiction. There is a section on forms of nonfiction writing, such as travel writing, sports writing, biographies, and business writing. There are a few paragraphs on the relationship between an author and an editor. This is useful information for a professional, and interesting for an amateur blogger like myself. There is a chapter on interviewing people too. It explains how to conduct an interview, how to quote people, and the ethical responsibility that a writer has to be faithful when using a quotation. The author also explains why you would want to quote someone in the first place. He uses quotations effectively himself, and these make his point very clear. The author includes a story about an article he wrote about Mount Rushmore. Instead of describing the place himself, he interviewed the people that worked there. I cannot think of a more evocative way of describing Mount Rushmore than one of the quotations he got:

"In the afternoon when the sunlight throws shadows into that socket," one of the rangers, Fred Banks, said, "you feel that the eyes of those four men are looking right at you, no matter where you move. They're peering right into your mind, wondering what you're thinking, making you feel guilty: 'Are you doing your part?'"

In short, On Writing Well is an informative book. It covers the whole craft of non fiction writing in about 300 pages and it is written well.

Comments

Popular posts from this blog

Learning Forth

One of my side projects for this year is to learn the programming language, Forth. Some people might consider this an odd language to learn. It is not a popular language. There are no hot startups using it (that I know of). It doesn't even show up in the top 100 languages in the TIOBE Index . However, I am convinced learning it is worthwhile. Some of my reasons for this are: Forth is probably the most successful and widely deployed language that nobody has heard of. It is the language used to develop OpenFirmware . This boot loader is installed on the laptops of the One Laptop Per Child Project , on PowerPC based Apple Mac computers, and on SPARC based computers from SUN Microsystems. It has also been used to develop to develop control software for the National Radio Astronomy Observatory , which is where it was developed. While not as widely used as C/C++, Forth is used a lot in embedded applications and has been ported to most micro-controllers. For example, the Forth, Inc. w

First Post

Hello and welcome to the inane ramblings of an Irish software developer. The title of the blog comes from Lewis Carroll's, Through the Looking Glass . In the book, Alice goes running with the Red Queen, but they don't seem to make any progress. Alice remarks on this, saying, "Well in our country, you'd generally get to somewhere else - if you ran very fast for a long time as we've been doing." The Red Queen replies, "A slow sort of country. Now, here, you see, it takes all the running you can do, to stay in the same place." The Red Queen Effect is quite applicable to the software industry, and as I probably will be talking quite a bit about the software industry, I thought it would be a good name for a blog. I have a few objectives for my new blog. By writing here, I hope to learn how to write well. That is, I hope to learn how to write clearly and concisely, and be interesting at the same time. I also hope that this blog will become a good prof

Operational Metrics and Alerts for Distributed Software Systems

This post will be about operational metrics and alerts for distributed software systems. What do I mean by that? I mean the metrics and alerts that allow operations personel to detect failure of of a distributed software system and helps them to quickly diagnose what is wrong. Metrics The metrics are measurements of characteristics of the system collected at regular(ish) intervals and stored somewhere for processing - rendering into graphs, triggering alert notifications, etc. Metrics can be divided into 3 categories: input metrics, output metrics, and process metrics. Input metrics are measures of the inputs to the system, for example, the number of user requests, counts of particular characteristics of the requests - where they are from, how large the request data is, counts of particular features in the request (for example, which resources/items/products are being asked for). Output metrics are measures of the output of the system. Examples of these would include orders s