You may notice your dog scratching his ear or rubbing it on the floor or on a piece of furniture. That's a sign that he may have a yeast infection. You should check his ears for these signs: (2)
• Brown, yellow or bloody discharge that has a strong odor
• Redness or swelling
• Crusted skin on the near ear flap
• Loss of hair around the ear
• Head shaking or tilting
• Loss of balance
• Loss of hearing
• Walking in circles
• Unusual eye movements*********************
I suppose you could tell if the dog was walking in circles by watching its ears. And even the head shaking and tilting might be evident. But the unusual eye movements? I'm going to be watching my dog's ears this evening. I'll tell you later what they say about her eyes.
© 2008 -- 2011 the Grandpa at The Word Mechanic. All rights reserved.
Showing posts with label work. Show all posts
Showing posts with label work. Show all posts
Tuesday, December 8, 2009
What Wonderful Ears
I was editing an article about yeast infections in dogs and found the following passage in the section about symptoms. In all fairness to the writer, she was rushed, and this was a rewrite, but still...
Saturday, October 31, 2009
A nightmarish week
My computer crashed last Sunday. I was trying to install the new Windows 7. But it got caught in an endless loop of rebooting. I couldn't even get a desktop. I spent the entire day Monday trying to get the issue settled with the help of someone from Microsoft spending four hours on the phone with me. The problem was that she didn't speak any known language. And the closest she came to English was repeating back to me the things I told her I tried, telling me that those were the things I needed to do. Finally she said she would have to put me on hold for ten minutes, would that be okay? I was tired of yelling at her that what she was asking me to do I had done already multiple times, both on my own and when she told me to do them, so I said yes put me on hold. She said she had to look for something . I hoped it was a translator. After five minutes, the phone disconnected. I supposed she had found what she was looking for and had no more reason to talk with me. Anyway, I didn't call back. I just spent the rest of the day doing those same things over again.
Then on Tuesday I got on my laptop and sent out emails to all my clients who had sent me stuff that I was supposed to be working on but which was locked as email attachments inside my failed office computer. Sometime close to noon a Microsoft guy supposedly in Cincinnati called me, said he knew about my problem (scary, no?), and he could help me solve it. After going back over what the problem was, he said the installation had failed and the computer was being tugged at by two operating systems, neither one of which could get control of it. "Oh," I said, "you speak English."
The man then asked if there were any important files on my computer. I asked him to repeat the question, and after I told him yes, he told me I needed to start Windows from the installation disk and do a "custom install."
I told him when I tried that before I got a warning saying it would wipe out everything on my computer -- all my writing, all my contracts, all my client lists, all my billing records and tax files. "Is that my only option?"
"Yes it is," he said. "But it won't wipe out your files. You'll just have to reinstall all your programs."
"All of them? It will take all of them?"
"Yes. But you just have to put the disks back in and reinstall them."
I didn't see any point in telling them that at least half of all the thousands of programs on my computer were downloaded, I had no disks for them, and I had no idea where the product keys for most of them were. Probably in a series of email archives. What would be the point? This was my only option.
So he talked me through the steps of getting the installation going. Once it was running, he said it would take a while and would it be all right for him to call me back in 45 minutes?
What the hell. "Sure," I said. "That will be fine."
The installation program crashed once. But I restarted it, and just as the second run was finishing up, the man in Cincinnati called me back and asked about the status.
When the computer was running and I had a desktop, he asked if he could take control of my computer and show me where my files were. "Okay," I said. But when he tried to locate them, they weren't in the folder where they were supposed to be. He did a search on a file extension and couldn't find anything. Then he asked for the name of a file. I gave him one and he searched for it. Then he found it, found the location of the folder it was in and added it to my "library." He then released control of my computer and said, "So now you see where they are?"
It's too late to make a long story short. But I can make it less long than it would be. I didn't see where they were, but I said yes, thanked him, and spent the rest of Tuesday reinstalling some programs and searching for my files. I got Outlook working, but couldn't find my email files to pull into it. I did find a folder that had program files in it. Some of them worked and some of them didn't. I went to bed that night thinking I was never going to work again.
Wednesday I kept looking for files. I started to figure out where they were. Still didn't have my email. Couldn't make my FileMaker database work. But I did feel I was making some progress.
Thursday I kept stabbing at the computer but also managed to get some of the work done that was scheduled for this past week. And by the end of the day Friday, I had managed to restore my database program, complete this past week's assignments, and even find my email files.
Now it's Halloween, but I'm not scared.
Then on Tuesday I got on my laptop and sent out emails to all my clients who had sent me stuff that I was supposed to be working on but which was locked as email attachments inside my failed office computer. Sometime close to noon a Microsoft guy supposedly in Cincinnati called me, said he knew about my problem (scary, no?), and he could help me solve it. After going back over what the problem was, he said the installation had failed and the computer was being tugged at by two operating systems, neither one of which could get control of it. "Oh," I said, "you speak English."
The man then asked if there were any important files on my computer. I asked him to repeat the question, and after I told him yes, he told me I needed to start Windows from the installation disk and do a "custom install."
I told him when I tried that before I got a warning saying it would wipe out everything on my computer -- all my writing, all my contracts, all my client lists, all my billing records and tax files. "Is that my only option?"
"Yes it is," he said. "But it won't wipe out your files. You'll just have to reinstall all your programs."
"All of them? It will take all of them?"
"Yes. But you just have to put the disks back in and reinstall them."
I didn't see any point in telling them that at least half of all the thousands of programs on my computer were downloaded, I had no disks for them, and I had no idea where the product keys for most of them were. Probably in a series of email archives. What would be the point? This was my only option.
So he talked me through the steps of getting the installation going. Once it was running, he said it would take a while and would it be all right for him to call me back in 45 minutes?
What the hell. "Sure," I said. "That will be fine."
The installation program crashed once. But I restarted it, and just as the second run was finishing up, the man in Cincinnati called me back and asked about the status.
When the computer was running and I had a desktop, he asked if he could take control of my computer and show me where my files were. "Okay," I said. But when he tried to locate them, they weren't in the folder where they were supposed to be. He did a search on a file extension and couldn't find anything. Then he asked for the name of a file. I gave him one and he searched for it. Then he found it, found the location of the folder it was in and added it to my "library." He then released control of my computer and said, "So now you see where they are?"
It's too late to make a long story short. But I can make it less long than it would be. I didn't see where they were, but I said yes, thanked him, and spent the rest of Tuesday reinstalling some programs and searching for my files. I got Outlook working, but couldn't find my email files to pull into it. I did find a folder that had program files in it. Some of them worked and some of them didn't. I went to bed that night thinking I was never going to work again.
Wednesday I kept looking for files. I started to figure out where they were. Still didn't have my email. Couldn't make my FileMaker database work. But I did feel I was making some progress.
Thursday I kept stabbing at the computer but also managed to get some of the work done that was scheduled for this past week. And by the end of the day Friday, I had managed to restore my database program, complete this past week's assignments, and even find my email files.
Now it's Halloween, but I'm not scared.
Monday, August 31, 2009
Bloopers
It's time to share some of my own writing bloopers. Here's two I made -- among several-- in an article I wrote today. The first one I caught before I sent the article to the editor. The second one I just saw.
1) I was writing about using plug-in timers that turn your lights on and off when you're away on vacation and I wrote:
"Look for timers that have battery backup so they'll still work if there's a power failure."
(I meant so the time would still be accurate.)
2) I just now saw this one:
"Always park your car in the garage with the garage door closed when you are there."
(That sounds dangerous no matter how you read it. I think I meant "Always leave your car in the garage with the garage door closed when you are home.")
1) I was writing about using plug-in timers that turn your lights on and off when you're away on vacation and I wrote:
"Look for timers that have battery backup so they'll still work if there's a power failure."
(I meant so the time would still be accurate.)
2) I just now saw this one:
"Always park your car in the garage with the garage door closed when you are there."
(That sounds dangerous no matter how you read it. I think I meant "Always leave your car in the garage with the garage door closed when you are home.")
Saturday, August 29, 2009
Thinking about the reader
Here’s the “lead” paragraph from an article for the web I edited the other day:
That one-sentence paragraph has 52 words and a Flesch-Kincaid grade level of 21.7. And can someone please tell me what a five-star alarm is? I know there is a product called a FiveStar Alarm that can be used to detect levels of dangerous gasses. So the writer may have been trying to use a metaphor, but I don’t think it works. I didn’t know there was such a product until I googled it, and I doubt many readers would know either. But what I really wonder is why a writer for whom English is not a second language would turn in an article with the phrase “they fear of being the girl who cried wolf." All that tells me is the writer didn’t bother to read any of the text before turning it in.
S and I were having dinner a few weeks ago with some close friends who are professional communicators like us, and at one point in the discussion the issue was raised about whether or not every assignment was equally important. J, an editor whose work I especially admire, said, “No, some assignments don’t matter. The job is just to get them out there.” Her point was that if an editor or a reporter treated every piece he or she is working on as if it needed to be perfect, the pieces that did truly matter might never get done.
I tend to agree with J. But that’s because I understand she wasn’t saying that there was any excuse for shoddy craftsmanship from a professional. And it doesn’t excuse a professional communicator for not considering the audience. You put out the best you can in the time you have with the attention it deserves. But if it isn’t clear, if it isn’t accurate, if the language isn’t at least used properly, you don’t present it.
If the writer of the one-sentence paragraph had any concern at all for the readers or for the subject matter, the paragraph might have looked like this:
For some expectant moms, even the slightest ache or pain can trigger a five-star alarm and trip to the doctor, but other pregnant women may well ignore a potentially serious warning sign because they think it is a normal part of pregnancy or they fear of being the girl who cried wolf.This is from a professional writer with an impressive list of credits, including Woman’s World magazine, Arthritis Today, and the Wall Street Journal. The writer has a graduate degree in journalism, and has won awards for online reporting. I can only assume the writer was having a bad day. (Actually, what I really assumed is that the writer is used to having her work very heavily edited and simply doesn't care.)
That one-sentence paragraph has 52 words and a Flesch-Kincaid grade level of 21.7. And can someone please tell me what a five-star alarm is? I know there is a product called a FiveStar Alarm that can be used to detect levels of dangerous gasses. So the writer may have been trying to use a metaphor, but I don’t think it works. I didn’t know there was such a product until I googled it, and I doubt many readers would know either. But what I really wonder is why a writer for whom English is not a second language would turn in an article with the phrase “they fear of being the girl who cried wolf." All that tells me is the writer didn’t bother to read any of the text before turning it in.
S and I were having dinner a few weeks ago with some close friends who are professional communicators like us, and at one point in the discussion the issue was raised about whether or not every assignment was equally important. J, an editor whose work I especially admire, said, “No, some assignments don’t matter. The job is just to get them out there.” Her point was that if an editor or a reporter treated every piece he or she is working on as if it needed to be perfect, the pieces that did truly matter might never get done.
I tend to agree with J. But that’s because I understand she wasn’t saying that there was any excuse for shoddy craftsmanship from a professional. And it doesn’t excuse a professional communicator for not considering the audience. You put out the best you can in the time you have with the attention it deserves. But if it isn’t clear, if it isn’t accurate, if the language isn’t at least used properly, you don’t present it.
If the writer of the one-sentence paragraph had any concern at all for the readers or for the subject matter, the paragraph might have looked like this:
For some expectant moms, the slightest ache or pain triggers a major alarm and a trip to the doctor’s office. But other pregnant women sometimes ignore a potentially serious warning sign. They may think it’s a normal part of pregnancy. Or they may simply not want to be seen as the girl who cried wolf.
Friday, July 17, 2009
I'm standing up for my writing
Literally.
I have some kind of sciatic nerve problem, or at least that's what the physician's assistant thought it was yesterday. It's aggravated by sitting at my desk, partly because I don't have good chair poster when I'm leaning over the keyboard working. After about an hour or so, my leg begins to hurt enough to make me very uncomfortable, and after about another hour, I can't bear to sit there any longer. The only thing that helps is to stand up and walk around. So I started last week standing at the kitchen counter to work when it got bad.
Last weekend I had to work both Saturday and Sunday, and I thought why even bother to sit down? So I used some wire shelving we have to hold my laptop and stood the whole day each day while I worked. I also found that in addition to my leg not hurting, standing let me think a little more clearly about what I was writing. Whenever I got stuck, I just walked around in a little circle and by the time I got back to the keyboard, the words I needed were there. So I kept standing all week long.
Yesterday when I saw the PA and she was giving me some exercises to do, she suggested that I should try to stand to work. (I told her that usually I could hardly stand to work, but I don't think she got it. So I just said OK.)
A few months ago I was working on an article about physical activity and I came across a research study that focused on the benefits of standing as opposed to sitting. It turns out that people who do their job mainly sitting (like bus drivers, for instance) have a tendency to die sooner than people who stand more. We all know about the value of exercise, but this was true even with low level physical activity. So maybe pain is not such a bad thing after all.
Here's the first draft of a poem I did today after coming across some notes I'd made for an essay. Too early to tell whether I like it or not, but I thought I'd share it.
The running of the ideas (first draft)
When the gates were opened for the running
of ideas, three men were trampled at the start.
Two more scrambled over the walls that lined
the street. And only the bravest stayed in front,
shouting the whole way, cheered on by rabble
leaning from the balconies above
and smiling critics -- middle-aged women and men
holding dry martinis, drinking rum.
At the ring the crowd roared as the first idea--
proud, brave, and very strong--gored the rider's
mount and threw the rider to the ground.
No one could slow him. No one could tire him,
until the bravest fighter of them all
stood before him and with his cape and grace
took pass after pass and brought him to his knees.
The crowd chanted its approval. They'd seen
a work of art. And the idea, its hind legs
lashed to the horse, was, without dignity
and without ears, dragged from the dusty ring.
© copyright 2009 the Grandpa at The Word Mechanic Blog.
All rights reserved
I have some kind of sciatic nerve problem, or at least that's what the physician's assistant thought it was yesterday. It's aggravated by sitting at my desk, partly because I don't have good chair poster when I'm leaning over the keyboard working. After about an hour or so, my leg begins to hurt enough to make me very uncomfortable, and after about another hour, I can't bear to sit there any longer. The only thing that helps is to stand up and walk around. So I started last week standing at the kitchen counter to work when it got bad.
Last weekend I had to work both Saturday and Sunday, and I thought why even bother to sit down? So I used some wire shelving we have to hold my laptop and stood the whole day each day while I worked. I also found that in addition to my leg not hurting, standing let me think a little more clearly about what I was writing. Whenever I got stuck, I just walked around in a little circle and by the time I got back to the keyboard, the words I needed were there. So I kept standing all week long.
Yesterday when I saw the PA and she was giving me some exercises to do, she suggested that I should try to stand to work. (I told her that usually I could hardly stand to work, but I don't think she got it. So I just said OK.)
A few months ago I was working on an article about physical activity and I came across a research study that focused on the benefits of standing as opposed to sitting. It turns out that people who do their job mainly sitting (like bus drivers, for instance) have a tendency to die sooner than people who stand more. We all know about the value of exercise, but this was true even with low level physical activity. So maybe pain is not such a bad thing after all.
Here's the first draft of a poem I did today after coming across some notes I'd made for an essay. Too early to tell whether I like it or not, but I thought I'd share it.
The running of the ideas (first draft)
When the gates were opened for the running
of ideas, three men were trampled at the start.
Two more scrambled over the walls that lined
the street. And only the bravest stayed in front,
shouting the whole way, cheered on by rabble
leaning from the balconies above
and smiling critics -- middle-aged women and men
holding dry martinis, drinking rum.
At the ring the crowd roared as the first idea--
proud, brave, and very strong--gored the rider's
mount and threw the rider to the ground.
No one could slow him. No one could tire him,
until the bravest fighter of them all
stood before him and with his cape and grace
took pass after pass and brought him to his knees.
The crowd chanted its approval. They'd seen
a work of art. And the idea, its hind legs
lashed to the horse, was, without dignity
and without ears, dragged from the dusty ring.
© copyright 2009 the Grandpa at The Word Mechanic Blog.
All rights reserved
Labels:
first draft,
health,
standing poetry,
work,
writing
Thursday, July 2, 2009
Problem/Solution
I know I haven't posted much about the agonies of editing recently. Wait. Come to think of it I haven't posted much of anything recently. Hmmmm. Well, anyway, as I was saying, I got this gem of a sentence today in an article about feeding an adult dog.
So...
.............. let's take a look at that sentence. First of all, it's 30 words. Now 30 words is a long sentence in an article aimed at an audience whose reading skills are defined as basic. The company I'm doing this work for defines basic as high school level. But that may actually be a little high for the general lay audience of adult readers they are trying to reach. When I edit or write for them, I shoot for an eighth grade reading level. (Which has nothing to do with the level of the intelligence of the audience. It only involves the ease with which the audience can take the information in.) The reason I aim for an 8th grade level is that a 6th grade level, which is more accurate, takes more time than they want to pay me for.
But this isn't really about reading level (or how much I get paid). It's about putting information in a sentence the audience can use. Now when we take a look at the sentence, it seems there's some important information in there. How do I know? Because there's a really impressive source being cited. Come on, we all know about the "National Research Council, a scientific research unit of the nonprofit National Academies," don't we?
PROBLEM # 1: Who says this (or "says what," because by the time I get to the end of the sentence I've forgotten what I was being told)? And why am I supposed to believe them? Their name sounds impressive. But who the hell are they? I just formed a group here in Atlanta where the CDC is located. We call ourselves the National Citizen's Healthcare Oversight Committee. Now we're probably going to be able to convince a lot of people about what we say. Why? Because we're right here where the CDC is.
Actually, my group is going to be more successful. Everybody has heard of the CDC. Well, not everybody, but enough. Can I have a show of hands. How many of you out there know what the "National Academies" are, or is it is?
Solution #1: Actually, I happen to know a little bit about both the National Academies and the National Research Council. But I'd have to Google them to be able to tell you who they are and what they do. And there was a paucity of hands raised just a moment ago.
So the first thing to ask as an editor is does the writer explain anywhere in the article who or what these agencies are? No. As a matter of fact, that is the only time their names appear in the article. So the solution seems easy. If you are going to call on an authority to vouch for your claim, then you need to make sure your readers know who that authority is. So the first option is to tell them.
But, no. That's a problem because it's going to take up a lot more space than it warrants and that's going to take the reader farther away from the real point of the article: What kind of dog food should I buy for my dog? (As I type this, Yeats is staring up at me with a hungry look in her eye. But then, she's still a puppy. Puppies are supposed to be hungry.)
The second thing I ask as an editor is do we really need the attribution. The answer is no. This is not a scientific paper for a peer reviewed journal. The website where this article will appear has a major reputation as an authoritative source. And underlying that is a rigorous fact checking and medical review process. Plus they hire good editors who are going to check these things out, even before the article gets to those stages. So we drop the attribution and come up with this:
Now that's much better. The message is clear with nothing about the National Academies to get in the way. It works because the website and the parent company have believability.
And look at that. I've actually solved two problems. I've cut the sentence in half. It's now just 15 words. A manageable chunk of information.
Problem #2: Yes there is a problem number 2. How do you calculate and confirm those percentages when you buy dog food. And I'll tell you that elsewhere in the article the writer pointed out that coming up with this information is hard because you can't rely on the label. And right. The writer didn't tell the reader how to determine the necessary percentages. Oh, me. An editor's work is never done.
Solution #2: Ignore the problem. Let the readers do some research of their own. You of course know that's not the correct answer. The correct answer is to send the article back to the writer and ask for more information. Taking the attribution out was an editor's call. Explaining how to figure the percentages is a writer's job.
Unfortunately, I didn't send it back. I didn't have time, and this article is part of a major launch, which is scheduled to happen very soon. My decision to let the article go as is was based on the fact that there was enough information in the article to make it useful and interesting and that it was an important part of the launch and needed to get into review. That was step 1 in figuring out a solution. Step 2 was realizing there really isn't enough time to make the article complete. It needs to go into review.
I would never knowingly make that kind of decision with an article that would involve injury. But now you know how articles that are less than perfect end up in print or on the web.
An adult dog's diet can contain up to 50% carbohydrates, including 2.5% to 4.5% fiber, according to the National Research Council, a scientific research unit of the nonprofit National Academies.
So...
.............. let's take a look at that sentence. First of all, it's 30 words. Now 30 words is a long sentence in an article aimed at an audience whose reading skills are defined as basic. The company I'm doing this work for defines basic as high school level. But that may actually be a little high for the general lay audience of adult readers they are trying to reach. When I edit or write for them, I shoot for an eighth grade reading level. (Which has nothing to do with the level of the intelligence of the audience. It only involves the ease with which the audience can take the information in.) The reason I aim for an 8th grade level is that a 6th grade level, which is more accurate, takes more time than they want to pay me for.
But this isn't really about reading level (or how much I get paid). It's about putting information in a sentence the audience can use. Now when we take a look at the sentence, it seems there's some important information in there. How do I know? Because there's a really impressive source being cited. Come on, we all know about the "National Research Council, a scientific research unit of the nonprofit National Academies," don't we?
PROBLEM # 1: Who says this (or "says what," because by the time I get to the end of the sentence I've forgotten what I was being told)? And why am I supposed to believe them? Their name sounds impressive. But who the hell are they? I just formed a group here in Atlanta where the CDC is located. We call ourselves the National Citizen's Healthcare Oversight Committee. Now we're probably going to be able to convince a lot of people about what we say. Why? Because we're right here where the CDC is.
Actually, my group is going to be more successful. Everybody has heard of the CDC. Well, not everybody, but enough. Can I have a show of hands. How many of you out there know what the "National Academies" are, or is it is?
Solution #1: Actually, I happen to know a little bit about both the National Academies and the National Research Council. But I'd have to Google them to be able to tell you who they are and what they do. And there was a paucity of hands raised just a moment ago.
So the first thing to ask as an editor is does the writer explain anywhere in the article who or what these agencies are? No. As a matter of fact, that is the only time their names appear in the article. So the solution seems easy. If you are going to call on an authority to vouch for your claim, then you need to make sure your readers know who that authority is. So the first option is to tell them.
But, no. That's a problem because it's going to take up a lot more space than it warrants and that's going to take the reader farther away from the real point of the article: What kind of dog food should I buy for my dog? (As I type this, Yeats is staring up at me with a hungry look in her eye. But then, she's still a puppy. Puppies are supposed to be hungry.)
The second thing I ask as an editor is do we really need the attribution. The answer is no. This is not a scientific paper for a peer reviewed journal. The website where this article will appear has a major reputation as an authoritative source. And underlying that is a rigorous fact checking and medical review process. Plus they hire good editors who are going to check these things out, even before the article gets to those stages. So we drop the attribution and come up with this:
An adult dog's diet can contain up to 50% carbohydrates, including 2.5% to 4.5% fiber.
Now that's much better. The message is clear with nothing about the National Academies to get in the way. It works because the website and the parent company have believability.
And look at that. I've actually solved two problems. I've cut the sentence in half. It's now just 15 words. A manageable chunk of information.
Problem #2: Yes there is a problem number 2. How do you calculate and confirm those percentages when you buy dog food. And I'll tell you that elsewhere in the article the writer pointed out that coming up with this information is hard because you can't rely on the label. And right. The writer didn't tell the reader how to determine the necessary percentages. Oh, me. An editor's work is never done.
Solution #2: Ignore the problem. Let the readers do some research of their own. You of course know that's not the correct answer. The correct answer is to send the article back to the writer and ask for more information. Taking the attribution out was an editor's call. Explaining how to figure the percentages is a writer's job.
Unfortunately, I didn't send it back. I didn't have time, and this article is part of a major launch, which is scheduled to happen very soon. My decision to let the article go as is was based on the fact that there was enough information in the article to make it useful and interesting and that it was an important part of the launch and needed to get into review. That was step 1 in figuring out a solution. Step 2 was realizing there really isn't enough time to make the article complete. It needs to go into review.
I would never knowingly make that kind of decision with an article that would involve injury. But now you know how articles that are less than perfect end up in print or on the web.
Thursday, June 25, 2009
This Fascinates Me
Ok. Cloudia caught me sitting at my desk and really made me feel guilty with her latest comment on my last post. (If you've never visited her at Comfort Spiral you are really missing something special.)
I promise I'm coming back to the Blogosphere soon. But I have been busy writing articles about the health benefits of having pets, Ewing's sarcoma, DTaP, and the like, and editing articles about things like rheumatoid arthritis or how to get your dog to eat dog food. (My days are simply eclectic.)
But I am coming back. In the meantime I found this little gem by the Ukulele Orchestra of Great Britain and thought you might enjoy it. (I was looking for a video of the theme to High Noon, but came across this instead and found it fascinating.) Have fun. And in the meantime, please do not forsake me. . .
I promise I'm coming back to the Blogosphere soon. But I have been busy writing articles about the health benefits of having pets, Ewing's sarcoma, DTaP, and the like, and editing articles about things like rheumatoid arthritis or how to get your dog to eat dog food. (My days are simply eclectic.)
But I am coming back. In the meantime I found this little gem by the Ukulele Orchestra of Great Britain and thought you might enjoy it. (I was looking for a video of the theme to High Noon, but came across this instead and found it fascinating.) Have fun. And in the meantime, please do not forsake me. . .
Thursday, April 30, 2009
Well this feels different
This morning, I finished the last piece of work in front of me that had a deadline. From 10 AM on, I have been unemployed. This is the first time since 1998 that I have not had at least one contract job still waiting on my desk to be done. I'm not worried. I have money coming in and there will be other work. It's just a strange feeling. It's also an opportunity. I can use the time to focus on doing more of my own creative work.
Thursday, April 9, 2009
The trouble with freelancing
A lot of people who do what I did don’t last as long at it as I have. I officially stopped working for the man and became a full-time freelancer in May of 1994. That means I’m starting my 16th year in just a few weeks. I know when I tell people I make my living from writing and editing, it sounds Romantic, like I’m living the life of a knight-errant or, since I do get to write poetry, some type of medieval minstrel. The reality is it’s more like the life of a vagrant, just roaming here and there with no visible means of support and no real goal in mind.
A lot of people I know who made the same leap, do it for three or four years, but then they go back and take a job. That's because we're not making our living by writing the things we love--great poetry, amazing fiction, soaring new journalism essays that fill the pages of The New Yorker. It's a small percentage of writers who get to earn money that way. What most of us do is called contract writing or work for hire. We work for agencies, pharmaceutical companies, health plans. We write very specialized pieces aimed at computer geeks, investment bankers, physical therapists, or people with diabetes. Getting to set our own schedule means never taking a day off because if you don't work, you don't get paid. And if you don't have any work in front of you at the moment, you have to scramble to find a client and pick up another assignment.
After a few years of doing that, of living in a constant state of uncertainty about where your next pay check is coming from, a job with paid sick time and vacation, with a 401K and office colleagues to talk to during the day seems mighty appealing. Even if your client list is pretty secure, it's that not having people to talk to during the day that can get very oppressive. I have, over the past fifteen years, gone back to teaching part time on occasion, not because I needed the money, but because I just needed the human contact.
I had perhaps my best financial first quarter since I started freelancing this year. I was busy. stretched completely to my limits. I was working so many weekends I'd have trouble knowing exactly what day it was. Things are finally quieting down and I can breathe a little easier. Except...
The end of March. Did you hear that crashing sound? That was the roof of my security shelter crashing down around me. Two long-term contracts that formed a solid monthly income base just ended. Just like that. Boston Globe Media decided not to continue publishing a magazine that I had been managing editing for them for 11 years. Not only did I feel I was getting laid off, but I had to contact the writers who wrote regularly for me and tell them I'd have no more work for them in the foreseeable future. Then right after I got that word I found out the newsletter for health care providers I had been writing for the past five or so years was not going to be published anymore, and the publishing company that did them was closing.
That's the the way business I'm in goes. I'll get more work. It's just that right now I'm feeling a little wistful for the job security of a tenured faculty member that I left to follow my dream. On the bright side, I am going to have more time to get back to the blog. I've missed it.
A lot of people I know who made the same leap, do it for three or four years, but then they go back and take a job. That's because we're not making our living by writing the things we love--great poetry, amazing fiction, soaring new journalism essays that fill the pages of The New Yorker. It's a small percentage of writers who get to earn money that way. What most of us do is called contract writing or work for hire. We work for agencies, pharmaceutical companies, health plans. We write very specialized pieces aimed at computer geeks, investment bankers, physical therapists, or people with diabetes. Getting to set our own schedule means never taking a day off because if you don't work, you don't get paid. And if you don't have any work in front of you at the moment, you have to scramble to find a client and pick up another assignment.
After a few years of doing that, of living in a constant state of uncertainty about where your next pay check is coming from, a job with paid sick time and vacation, with a 401K and office colleagues to talk to during the day seems mighty appealing. Even if your client list is pretty secure, it's that not having people to talk to during the day that can get very oppressive. I have, over the past fifteen years, gone back to teaching part time on occasion, not because I needed the money, but because I just needed the human contact.
I had perhaps my best financial first quarter since I started freelancing this year. I was busy. stretched completely to my limits. I was working so many weekends I'd have trouble knowing exactly what day it was. Things are finally quieting down and I can breathe a little easier. Except...
The end of March. Did you hear that crashing sound? That was the roof of my security shelter crashing down around me. Two long-term contracts that formed a solid monthly income base just ended. Just like that. Boston Globe Media decided not to continue publishing a magazine that I had been managing editing for them for 11 years. Not only did I feel I was getting laid off, but I had to contact the writers who wrote regularly for me and tell them I'd have no more work for them in the foreseeable future. Then right after I got that word I found out the newsletter for health care providers I had been writing for the past five or so years was not going to be published anymore, and the publishing company that did them was closing.
That's the the way business I'm in goes. I'll get more work. It's just that right now I'm feeling a little wistful for the job security of a tenured faculty member that I left to follow my dream. On the bright side, I am going to have more time to get back to the blog. I've missed it.
Wednesday, February 4, 2009
This is just to say (and I've lost two followers over night)
Rae at US IN TEJAS tagged me for a meme. And Marty at Dark Star Discovery (what a wonderful Blog name) won two awards and passed them along to me. Thank you, both of you. Considering the fact I've been totally AWOL from the Blogosphere for way longer than I ever thought I'd be, and will for more days ahead, I'm touched. I'll do the meme and post the awards and pass them on soon. But again, thanks.
Subscribe to:
Posts (Atom)