|
By Mike Gunderloy
Monday, August 25, 2003
I've been prevailed upon to offer some advice to new writers in the computer field. I don't know how many articles this will take, or how often I'll get them out, but here's a start. If you've been reading Larkware for a while you probably have a feel for my credentials already, but just in case you care, here's a link to my CV in Microsoft Word format.
I'll start by talking about articles, and get to books later. I think this makes sense, because most writers will want to start with articles; they're less threatening and pay more per word. (So why write books? Better for self-promotion, mostly). Just about anyone can get a contract to write an article for the computer press. The trick is to get into a relationship where the editor wants you to write more articles. Here's a short list of ways you can help make that happen:
- Know what sort of articles the magazine publishes before you approach the editor. If you pitch something wildly inappropriate in subject matter or length, they'll know that you didn't even bother to read the magazine first.
- Write about something you actually know. Don't misrepresent yourself. It's OK to write about something you're learning as long as you learn enough to do a thorough job with the article.
- Ask for a copy of the magazine's style sheet, author kit, or Word template - whatever they've got as guidelines for writers. Read the guidelines and follow them.
- Make sure the article is technically correct. This is more important that making sure the grammar is perfect. The magazine will employ people who can fix your spelling and grammar, but they can't fix your code.
- Find out what requirements the magazine has for figures (format, DPI, color depth) and make sure you follow them.
- Write all the little things that go with the article: your bio, headings and sub-headings, table and figure captions.
- If the magazine makes sample code available, send it in with your article (and mention it when you pitch the article -- all other things being equal, an article with sample code will get bought in preference to an article without sample code). Make sure the sample compiles and runs!
- Don't get too attached to your deathless prose, because the editor will change it. A good editor will improve your writing, but any editor will change it. In this respect editors are the same as dogs; when they see something new, they simply must mark it with their own scent.
- No matter how good or bad your writing, at least run the spell-checker and do your best to write in English.
- If the magazine supplies a Word template, use it. If necessary, the editor will do the extra work to pour your article into their template, but they won't like it.
- Find out what the deadline is for the article, and meet it. Don't agree to a deadline you can't meet. If something comes up that will prevent you from making the deadline, give the editor as much warning as you possibly can so that they can fill the space.
- Write simple, direct sentences. Use short words instead of fancy ones (unless you need the fancy ones for a technical point). Use active voice ("I added two button controls to the form") rather than passive voice ("Two buttons were added to the form"). Don't use "we" when you mean "I" (the author) or "you" (the reader).
Mike Gunderloy is the lead
developer for Larkware and author of numerous books and articles on programming
topics.
|
|