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.
Subject:Re: screen dumps in books From:"Brierley, Sean" <Brierley -at- QUODATA -dot- COM> Date:Mon, 18 Jan 1999 15:47:34 -0500
Thanks.
>>>The important part of your question, however, is how to get this
>>>across to "programming" -- somehow, you've gotten yourself into a
>>>situation where you are not viewed as the expert. You need to
>>>establish yourself as the authority here, otherwise "programming"
>>>is going to walk all over you.
Yes. I agree. I have been here maybe eight weeks. This situation, I
believe, was made for me. I address some of these issues by asking
"programming" questions like "why do you think that?" After
"programming" pauses for an extended period, as they do, I explain why I
have a different view. This, I notice, has caused some chin dropping.
However, I really do not want to be entirely antagonistic. I haven't yet
offered an opinion on their programming, structure, or code.
If anyone else has advice on helping me turn this corner, I'd appreciate
it. Yes, I have bought beers for key programmers and do participate in a
network game or two at lunch--as well as table tennis, which is where I
schmooze "Sysop."
42. I read that book, those books, twenty years ago (has it really been
that long?). I remember waiting for the next in sequence to be published
(the fourth and fifth didn't do much for me, though). Anyway, I still
remember them clearly and now I must go buy them.
