Categories
Writing

Missouri Review on writing current events

From the weblog of the Missouri Review on why most submissions related to current events are seldom accepted by the publication. The entire post is excellent, but one point in particular stood out:

Most writers can’t realize their ambitions because they are writing out of something like reflex, and according to a mistaken assumption that they understand more than they do about a headline event. Even the most perceptive among us are misled by the media, which intentionally creates a sense of intimacy about headline stories, in part by providing a variety of angles that will hook the broadest audience possible. I’m not saying that’s bad. It’s a fact. We’re lured by the intensive coverage into becoming voyeurs. […] But the sad thing about voyeurism is that it doesn’t generate understanding or true knowledge. Many of the submissions we receive about headline stories are well enough made and written, but thin on comprehension of the real, true event. The writers are earnest, but they mistake their media-taught familiarity with the visible surface for a deeper understanding of what lies beyond it.

Do read the entire post–it’s relevant to all writers.

Categories
Writing

Missouri Review on writing on current events

From the weblog of the Missouri Review on why most submissions related to current events are seldom accepted by the publication. The entire post is excellent, but one point in particular stood out:

Most writers can’t realize their ambitions because they are writing out of something like reflex, and according to a mistaken assumption that they understand more than they do about a headline event. Even the most perceptive among us are misled by the media, which intentionally creates a sense of intimacy about headline stories, in part by providing a variety of angles that will hook the broadest audience possible. I’m not saying that’s bad. It’s a fact. We’re lured by the intensive coverage into becoming voyeurs. […] But the sad thing about voyeurism is that it doesn’t generate understanding or true knowledge. Many of the submissions we receive about headline stories are well enough made and written, but thin on comprehension of the real, true event. The writers are earnest, but they mistake their media-taught familiarity with the visible surface for a deeper understanding of what lies beyond it.

Do read the entire post–it’s relevant to all writers.

Categories
Books Writing

With appreciation

his week is the last week for editing on the new book, and the editors are just now finishing up. I wanted to thank the folks who gifted me with their time and effort; providing reviews, technical and other editing, and suggestions. I had a good group of people and the book is going to be a superior product based on their effort:

Roger Johansson of 456 Berea Street was spot on with CSS, issues related to accessibility, as well as general markup and page design. He also managed to catch numerous typos.

Elaine Nelson of Emergency weblog provided not only tech editing, but also did an excellent job of content editing.

Roy Owens — not the singer. Roy also helped me on Learning JavaScript. Some people are gluttons for punishment.

Anne Zelenka of Anne 2.0 provided a higher level analyst view, as well as spotting gotchas, areas of confusion, and points of information that should have been included, but weren’t.

Jesse Skinner, from The Future of the Web who is an expert on unobtrusive Ajax, and is currently working on a Short Cut for O’Reilly on unobtrusive Ajax. Jesse specifically focused on the tech, and his extensive knowledge of the Ajax world was extremely valuable.

Anthony Holdener, who is writing O’Reilly’s Definitive Guide to Ajax, contributed edits for the first three chapters until he had to return to his book. I appreciate the extra effort.

Kathy Sierra, of Creating Passionate Users did a first chapter review and provided some excellent insight into refocusing the first chapter and making important points more discernible.

My main editor, Simon St. Laurent, of course. This is my third book with Simon. Did I mention, gluttons for punishment?

It is a lot of work to review a tech book. You’re not just reading the book, you’re:

  • looking for typos
  • looking for missed opportunities
  • watching out for uses of technology that could be improved
  • watching out for uses of technology that really need to be improved
  • helping to discover areas where the author has made a mistake (all authors make mistakes)
  • helping to sooth and tame wild, clumsy, and agitated phrases
  • doing all of this within the constraints of an awkward book template, under deadline, with an overly tired author

The editing team for a book is the author’s only support in what is a difficult task. They form the parachute when we’re free falling; the additional sets of eyes when our own are tired and strained. Of course, the editing team can also only do so much: in the end, whatever is missed is ultimately the responsibility of the author.

Thank you. Thank you all most sincerely, from the bottom of my book writing heart.

Categories
Writing

Short takes

The editing process can be fraught with possibilities for humor, especially when looking at typos. In one example, the text of the sample web site talked about “Poor the margarita into a glass”, leading to expressions of sympathy from my editors. My favorite so far, though, is “Transversing collections of data..” instead of “Traversing collections of data…”.

Alternate lifestyle code, indeed.

I’d already found the occurrence of “can’t” misspelled with a ‘u’ before sending it off for editing. Good thing, too, as editors never let you forget slips like this. Ever.

Speaking of geekery, OpenID is now the new cat’s jammies. For those new to this darling, all you really need is a bit of open source software and a URI, and it magically opens doors for you everywhere. I had an OpenID URI once but found it too blasè. I know what I really want, but unfortunately, iamgod.com, is already taken.

Categories
Books Writing

Finished the Draft

I finished the book draft today. I don’t remember ever being so tired when I’ve finished a book, previously. Perhaps it’s the cumulative effects of all the words written, code samples created, proofs read, edits made, reviews read with trepidation.

Next week I need to review the errata for the Learning JavaScript book, so those making the language translations can start with clean copy. Then on to the Adding Ajax editing. By the first of March, I’ll be ready for a break. During that time, I might see what I can do incorporate some of the stuff I wrote about into my own sites.

Books, that now makes lots of books:

Powerbuilder 5.0 How-To, July 1996

Special Edition Using PERL 5 for Web Development, October 1996

JavaScript 1.0 How-To, December 1996

Dynamic Web Publishing, December 1997

A couple of chapters for a book on Perl that I can’t remember the name of the book’s title.

Java 1.1 Unleashed, 1997

Maximum Java 1.1, 1997

The Power Guide to Dynamic HTML, January 1998

Developing ASP Components, 1999

Developing ASP Components, 2nd Edition 2001

Essential Blogging, 2002

Unix Power Tools, November, 2002

Practical RDF, 2003

Learning JavaScript 2006

and now…

Adding Ajax, with estimated publication in June, 2007