Monday, December 22, 2008
Thursday, December 04, 2008
Life in a Day is going to Kill Me
Oh, my.
I've just received an interesting task. I am to watch a movie, then write a blog post on it.
For pay.
Labels: A Life In A Day, blog, movies, work, writing
Monday, November 03, 2008
Thursday, September 18, 2008
Fourteenth Hour
"It's your blog".
That's what G. said when I asked him a few minutes ago if it was time for another blog. The sharp response provoke the following topic.
Does one write posts for an audience or oneself? That's an extremely common question many bloggers ask themselves and even their readers. Who (or is it whom?) is one writing for? Since I write blog posts for pay, I'm in an interesting position to see both sides of the question.
And my opinion? It's both, naturally. I consider blog posts similar to short stories, novels, comic books, and any other auditory/visual medium (e.g., paper, webpage, podcasts, etc.) where an author tells/writes their thoughts so others can experience it. Posts, on the one hand, can be read by almost anyone depending on the permissions given (or how skilled is the hacker). If the blogger truly wanted to keep things for themselves, they wouldn't be publishing their posts.
On the other hand, bloggers need a source to tap for their topic and that's themselves. Yes, one can give a blogger a subject matter to write about, but their viewpoint, writing style, etc., is theirs -- and theirs alone. The blogger decides how much of themselves they're willing to bare not only to their readers, but themselves as well. As G. above recently said, he hates re-reading his reviews, something he shares with all writers. That's understandable, for every time one writes their thoughts down, they give something of their thoughts and hearts, which is not always pleasant to look in the stark light of reality.
--
Carpe Diem (seize the day)
That's what G. said when I asked him a few minutes ago if it was time for another blog. The sharp response provoke the following topic.
Does one write posts for an audience or oneself? That's an extremely common question many bloggers ask themselves and even their readers. Who (or is it whom?) is one writing for? Since I write blog posts for pay, I'm in an interesting position to see both sides of the question.
And my opinion? It's both, naturally. I consider blog posts similar to short stories, novels, comic books, and any other auditory/visual medium (e.g., paper, webpage, podcasts, etc.) where an author tells/writes their thoughts so others can experience it. Posts, on the one hand, can be read by almost anyone depending on the permissions given (or how skilled is the hacker). If the blogger truly wanted to keep things for themselves, they wouldn't be publishing their posts.
On the other hand, bloggers need a source to tap for their topic and that's themselves. Yes, one can give a blogger a subject matter to write about, but their viewpoint, writing style, etc., is theirs -- and theirs alone. The blogger decides how much of themselves they're willing to bare not only to their readers, but themselves as well. As G. above recently said, he hates re-reading his reviews, something he shares with all writers. That's understandable, for every time one writes their thoughts down, they give something of their thoughts and hearts, which is not always pleasant to look in the stark light of reality.
--
Carpe Diem (seize the day)
Labels: A Life In A Day, confession, experiment, opinion, writing
Thirteen Hundred
Don't you hate it when technology fails you and you don't know why?
That just happened to me. Here I am, doing my work, copying and pasting some text from a Microsoft Word document to Notepad. Why? Let's just say Microsoft likes to hide code which doesn't like non-Microsoft products (and even some other MS products).
Anyway, I select Ctrl and V keys to paste the selected text. What do I see? Well, I see text but it's the wrong one. What the frak? I think. Instead, I see the text from the prior copy/paste job.
A bit of explanation. MS Word apparently has a feature that records a certain number of copy/paste jobs in the Paste functionality. Normally it defaults to the most recent copy when pasting text. However, one can open this job list to paste in earlier material. I never use the feature, since I copy/paste what I want to paste the first time.
Anyway, I try again, copying the right text, then paste again. Still old stuff. Argh! This time I cut the material from the Word document, confident I could restore it using the Undo feature. Nope. Argh! (I'm beginning to sound like a pirate, eh?) I undo the Cut, then give up. I've dealt with this admittedly rare issue in the past and know of only one way to stop it. Yup. That's right. Reboot.
Grrr....
--
Carpe Diem (seize the day)
That just happened to me. Here I am, doing my work, copying and pasting some text from a Microsoft Word document to Notepad. Why? Let's just say Microsoft likes to hide code which doesn't like non-Microsoft products (and even some other MS products).
Anyway, I select Ctrl and V keys to paste the selected text. What do I see? Well, I see text but it's the wrong one. What the frak? I think. Instead, I see the text from the prior copy/paste job.
A bit of explanation. MS Word apparently has a feature that records a certain number of copy/paste jobs in the Paste functionality. Normally it defaults to the most recent copy when pasting text. However, one can open this job list to paste in earlier material. I never use the feature, since I copy/paste what I want to paste the first time.
Anyway, I try again, copying the right text, then paste again. Still old stuff. Argh! This time I cut the material from the Word document, confident I could restore it using the Undo feature. Nope. Argh! (I'm beginning to sound like a pirate, eh?) I undo the Cut, then give up. I've dealt with this admittedly rare issue in the past and know of only one way to stop it. Yup. That's right. Reboot.
Grrr....
--
Carpe Diem (seize the day)
Labels: emotion, experiment, work, writing
