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: Getting that info From:Reshma <reshma_pendse -at- yahoo -dot- co -dot- in> To:Anne Robotti <arobotti -at- gmail -dot- com> Date:Tue, 5 Mar 2013 22:32:51 +0530
I've managed SE for my team for a long time now. It definitely gets you taking to Support and gives you an insight on just what kind of information would reduce customer bugs. Also Dev love it when I push back on hot fixes to Support saying its not justified. We don't have dedicated SE so any time they spend on support issues is time not spent on feature development. When they get that I'm on their side and providing better doc makes their life easier, they are great. Last sprint, they actually allocated one developer to just help me gather all the technical info from the team for the customisation guide. Sweet!
Regards,
Reshma
Sent from my iPhone, please ignore typos.
On 05-Mar-2013, at 11:57 AM, Anne Robotti <arobotti -at- gmail -dot- com> wrote:
> At one job I discovered so many bugs, weirdnesses, and unexpected results
> in the software they gave me a QA login so I could log issues directly. And
> I was really proud of that. I banged on it 'til it broke, over and over.
> I've found that developers find it reassuring that I come to them with
> specific questions about the behavior of the software, *after* I've read
> the available documentation and even the marketing materials. I like the
> big picture. "What are we telling the end users it does? What are they
> going to want to do with it? What are all the things that might happen when
> they try to do that?" I don't always write it all, but I like to know it.
> Real interest in the software goes a long way toward getting time with the
> developer - once they realize I'm not going to waste their time, they're
> usually happy to talk about the specifics of their work.
>
> Anne
>
>
>
>> On Sun, Mar 3, 2013 at 11:53 PM, William Sherman
>> <bsherman77 -at- embarqmail -dot- com>wrote:
>>
>>> [...]After all, being a TECHNICAL writer means I should learn and
>>> understand the technical aspects, not just write what some person told me
>>> to write.
>>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> EPUB Webinar: Join STC Vice President Nicky Bleiel as she discusses tips for creating EPUB, the file format used for e-readers, tablets, smartphones, and more.
>
> Learn more: http://bit.ly/12LyN2z
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> You are currently subscribed to TECHWR-L as reshma_pendse -at- yahoo -dot- co -dot- in -dot-
>
> To unsubscribe send a blank email to
> techwr-l-leave -at- lists -dot- techwr-l -dot- com
>
>
> Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
>http://www.techwhirl.com/email-discussion-groups/ for more resources and info.
>
> Looking for articles on Technical Communications? Head over to our online magazine at http://techwhirl.com
>
> Looking for the archived Techwr-l email discussions? Search our public email archives @ http://techwr-l.com/archives
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
EPUB Webinar: Join STC Vice President Nicky Bleiel as she discusses tips for creating EPUB, the file format used for e-readers, tablets, smartphones, and more.
