TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
>And in fact, how can you even prove that *anything* is your own work, even when it is?<
By being able to discuss your work intelligently and coherently, off the cuff, in a person-to-person situation such as an interview springs to mind.
This brings us back to an earlier comment from Gene, I believe, about how important it is to use a variety of factors -- from written samples, to on-site testing, to grilling people to see if they are bluffing or can actually walk the walk, to some special kind of intuitive spidey-sense built on years of experience -- to determine which applicants are worth hiring. And I think that is what's getting people's danders up about the certification process as proposed.
If no Tech Comm. Manager in their right mind would hire somebody based solely on a pile of pre-packaged self-evaluations and samples, then it seems a bit odd to award professional certification that way. Especially since the standards/criteria for qualifying aren't defined; and everything about the process, instructions, etc. is vague and confusing.
-----Original Message-----
From: techwr-l-bounces+lynne -dot- wright=tiburoninc -dot- com -at- lists -dot- techwr-l -dot- com [mailto:techwr-l-bounces+lynne -dot- wright=tiburoninc -dot- com -at- lists -dot- techwr-l -dot- com] On Behalf Of Janoff, Steve
Sent: Friday, October 21, 2011 2:37 PM
To: techwr-l -at- lists -dot- techwr-l -dot- com; 'Peter Neilson'
Subject: RE: Original work [was RE: STC certification program: skeptical curmudgeonlyness, part II]
What I'd think she could do in that case is use the original report she wrote as a sample in her portfolio, but also keep a copy of the VP's report to show that it was used later.
What the VP did was a form of internal plagiarism, but then again not because as the attorney points out, the original report was a work made for hire. I can't tell you how many times I've seen this happen over the years in my career, where someone would take the work of others and claim it as their own. I'm sure pretty much everyone on this list has experienced that, either with their own work or others'. That's a rampant thing in corporations. But, that's the way it is. I will say that I've seen it have a major effect on how people work. I don't know what the answer is on this one. It has to do with attribution of work product. In the free market, there are laws. In the internal world of the corporation, the corporation *is* law. (At various companies I've seen people hide work until release time so that it wouldn't get ripped off and show up in someone else's earlier release before the writer was acknowledged as the "author.") The open source world might have a
solution but I don't know enough about that. It's my belief, though, based on what I've seen, that in the corporate world a lot of creativity and innovation has been stifled due to these concerns.
And in fact, how can you even prove that *anything* is your own work, even when it is?
Steve
-----Original Message-----
From: techwr-l-bounces+sjanoff=illumina -dot- com -at- lists -dot- techwr-l -dot- com [mailto:techwr-l-bounces+sjanoff=illumina -dot- com -at- lists -dot- techwr-l -dot- com] On Behalf Of Peter Neilson
Sent: Thursday, October 20, 2011 9:40 AM
To: techwr-l -at- lists -dot- techwr-l -dot- com
Subject: Re: Original work [was RE: STC certification program: skeptical curmudgeonlyness, part II]
On Thu, 20 Oct 2011 11:37:15 -0400, Gene Kim-Eng <techwr -at- genek -dot- com> wrote:
> of the writers could have pointed to a finished document a month after
> it was done and they had gone on to the next and said "I did this part.".
More skepticaler curmudgeonlyerness ...
There is the issue of ghost writing. My wife (the quality engineer) wrote a report for one company where she worked. The report went into the corporate hopper, and she didn't see it again until ...
... she was at a conference months later and someone said to her, "You might be interested in this report that your company's VP of research wrote. Take a look."
"But I wrote that!" she said. "He put his name on it and didn't change a thing."
There's no way she can ever claim that report as hers.
Eventually she mentioned the situation to a lawyer. "If you wrote it for that company, it's theirs, not yours. They can do whatever they want with it. It's not yours."
- - -
With few exceptions, all tech writing that I have produced that actually has my name attached is from longer than 20 years ago. I really do not know how I would establish that I wrote the useless but proprietary material that I might still have, lurking on old 1.44 floppies in the back of a closet. That was part of a failed project several years ago. The failure itself was spectacular, and I may have triggered it...
... "I'm told you can tell me about the XX that I need for the B project,"
I said. "Huh? What's that?" So I explained. "Oh," said my high-level SME.
"The B project. I didn't know about that. That'll never happen." About a month later they pulled the plug, after having spent millions. And I have the floppies with the incomplete tables and charts, some of which I helped adjust.
Is that crap my portfolio? I worked really hard on the B project for months.
Create and publish documentation through multiple channels with Doc-To-Help.
Choose your authoring formats and get any output you may need. Try
Doc-To-Help, now with MS SharePoint integration, free for 30-days. http://www.doctohelp.com
---
You are currently subscribed to TECHWR-L as Lynne -dot- Wright -at- tiburoninc -dot- com -dot-
Create and publish documentation through multiple channels with Doc-To-Help.
Choose your authoring formats and get any output you may need. Try
Doc-To-Help, now with MS SharePoint integration, free for 30-days. http://www.doctohelp.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
