Think of a typical writer: slightly introverted, non-athletic, and of course, bespectacled. There are certainly many exceptions to this stereotype, but most of us fit the image to varying degrees. One characteristic that is rarely ever assigned to writers is that of fighter. Sure, we may wield the poison pen from time-to-time, but rarely do we become full-fledged mixed-martial artists. However, there is one contentious topic that will make even
Archives for January 2013
Comparing copywriting and technical writing is like comparing kiwis and potatoes, right? One is fuzzy, tropical, and sweet—and the other is an underground tuber associated with European famine. But, is the difference between copywriting and technical writing really this drastic? As both a copywriter and a technical writer, I don’t think so. Copywriting traditionally relates to marketing activities. Think direct mail, advertisements, press releases, and brochures. On the other hand,
I am going to conclude our current discussion on file naming with some shocking news. Sometimes you have to ditch your protocol. Yes, chuck it, trash it, leave it by the wayside. Now, I know what you’re thinking: Why would I spend three previous posts (Part 1, Part 2, Part 3) extolling the glorious virtues of file naming protocols only to turn around and tell you not to use one?
To rename or not to rename ….that is the question! Okay, so I’m being a bit dramatic, but renaming existing files can create unexpected trouble later on. I learned this the hard way during a most inconvenient time—tax time. Each February, I download the newest version of my preferred tax software, which then imports the old tax records stored on my computer. The program uses these old files to auto-fill
In the last post, we discussed the importance of establishing a file naming protocol. While creating said protocol is not particularly difficult, here are a few tips to keep in mind: 1. Blank spaces are like germs, avoid them. Most of today’s desktop programs allow blank spaces in file names. However, spaces can cause database problems, so if there is any chance at all that your files will be stored