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.
>>3 The knowledge that your sources of information that will dry up because
>>everyone's going to avoid telling you anything for fear that you'll decide
>>you don't like something for whatever reason and will become that point's
>I'm not really a knight errant, I'm more like a bird dog. I point, they
>shoot. Or not. It's up to them.
He did point. He did shoot. The PM spoke. He should make sure his notice to
the PM is in writing, and maybe he could CC his boss. My problem is deciding
that the response wasn't what he wanted, so he should run over to a
department that may or may not be technically adept with a scare that may or
may not be valid.
>>4 The knowledge that when they fire your butt for sticking your nose where
>>it doesn't belong and having customers cancel orders, you will have enough
>>money saved to handle the long period of unemployment.
>No doubt this is true in places that are highly politicized, where the
>success of the product is secondary at best, and where departments lie to
>one another as a matter of course. I've never worked in such places or had
His place seems to be one of those politicized environments. He's at his
place, not yours. If it was yours, by your description, he wouldn't have the
dilemma in the first place.
>Perhaps it's my years of management, but whenever a new fact crops up, one
>of the first questions I ask myself is, "Who needs to know?" Often
>execute badly because no one asked themselves this question, and people who
>are vitally interested don't find out until it's too late for them to react
He did. He made the project manager aware. The PM determined a course of
action. The problem I have is the advice that since the PM didn't react the
way he wanted, then it was up to him to try to find someone who would, even
if it was to go around him.
>>>Product X is intended for financial institutions, where security is
>>>important. There's a login/password authentication system. But, the
>>>product uses Internet Explorer as the interface. It's easy to bypass
>>>the system. I documented that, but the product manager told me to take
>>>it out, not because it wasn't true, but because he didn't want people
>>>to know it worked that way.
>>To do this requires the following:
>>1 An exceptional understand of exactly what it is in the interface that
>>makes you absolutely positive that the security breach applies to your
>>product, in the exact situation it is being used, with no possibility that
>>it isn't addressed by some other means some other place in the
>This was taken as a given from the problem, as presented.
I don't see that level of understand from the description. The post said:
>>>the product uses Internet Explorer as the interface. It's easy to bypass
That's an in-depth understanding? For all we know, the poster simply knows
that IE has security holes.
Senior Technical Writer
jposada -at- book -dot- com
Although she lives with seven other men, she's not easy.
------ Magic Mirror
Purchase RoboHelp X3 in April and receive a $100 mail-in
rebate, plus FREE RoboScreenCapture and WebHelp Merge Module.
Order here: http://www.ehelp.com/techwr-l/
You are currently subscribed to techwr-l as:
archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.