Book Editing By Dummies
Something happened back in November of 2008. Apparently I lost my mind and agreed to write a book alongside an established author of SQL Server technical books, Louis Davidson (@DrSQL on Twitter.) I’m not sure if it was the drinks and the Zig Zag, or perhaps the strong Seattle coffee and fresh Pacific Northwest air.
Being an Author (capital “A” in this case) had been a longtime dream of mine. I grew up being a voracious reader, and like many hardcore readers I had that yearning to jump to the other side of the pen. One day I wanted to be like Stephen King. In a manner of being, it did happen. I feel like I was walking along a rural road and just got clipped by a poorly-driven late model panel van. I came to this karmic realization tonight as I was reviewing Louis’ chapter on DMVs for Query Plans.
In 6 years I’ve gone from simply reading Microsoft SQL Server books to reading and writing and editing them. I used to think it was always hard to read them without falling asleep. What I never realized was how hard the Writers and Editors have it. I have a deep appreciation for all those who’ve come before me; and those to come after. If any of you out there reading this (and I know who all 4 of you are) then may I suggest starting out as a forum author. Search out those who need help on the various forums and pick a few each day that you feel comfortable answering, then do it. From there perhaps submit articles to sqlservercentral.com, mssqltips.com, sqlserverpedia.com, sqlteam.com, or sql-server-performance.com. These sites are all run by stellar individuals who clammor for writing talent. After that, who knows? Perhaps you’ll be pulling your hair out on a Saturday night writing about transactions, spids, and query handles.
Editing articles and books is a pretty hellish job. Tony is the best editor I’ve ever come across, but even he likes to break out and do something else occasionally. I haven’t the mental discipline to do it.
The golden rule for authors is that the editor is almost always right, just because he/she can stand outside, looking in. the author can’t, so is blind to his, or her, faults.
[…] Book Editing By Dummies – the author’s name goes on the front, but the editors and reviewers are the ones who make sure the author looks good. I echo Tim’s sentiments about the shock of how fast your career can move once you get involved with PASS – one day you’re trying to decide what book to buy at the bookstore, and the next day you’re trying to figure out how to phrase things in the book you’re writing or editing! […]
[…] Find Orphaned AD Logins using sp_validatelogins | SQLBatman.com on Using xp_logininfo to Determine Membership in Active Directory Group · Syndicating Your Blog at SQLServerPedia | Brent Ozar – SQL Server DBA on 2008 Music Wrap Up – Zune …Next Page […]
I don’t know. I started writing books because I never felt good about articles that didn’t cover enough. I never want to tell just enough to make you hungry when I am interested in the subject. I blog tips, tricks, and ideas, but a book can tell (almost) everything about the subject.
And there is the problem. To “tell” everything, you have to “find” everything. Note I didn’t say “know” it, because I find writing to be 1/2-3/4 what you know, coupled with 1/2-3/4 what you find out for the book. (I know, the math doesn’t work out neatly, and neither does most books.)
Having written a few and tech edited a few, the fact is that it is a miracle any books finish. Almost all tech edited material from us part-timer is pretty terrible. The basics are usually there, but so many mistakes because we are working like crazy with no time to spare.
Then comes the tech editor job. No, no, no, interesting, I didn’t realize that, No, No, No. A good tech editor is in ways, more important than the writer, though it takes less time and gets paid less and has much less glory 🙂