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.
Re: Working with developers (was Re: About The Cloud: Quick-Read Suggestions)
Subject:Re: Working with developers (was Re: About The Cloud: Quick-Read Suggestions) From:Anne Robotti <arobotti -at- gmail -dot- com> To:Keith Hood <klhra -at- yahoo -dot- com> Date:Thu, 4 Apr 2013 06:44:27 -0400
I've gotten on the good side of many a developer with the phrase, "I booked
an hour, but I've really narrowed it down to one question, can I just ask
it and get out of your way?" Also, application access helps - I get it the
first day in a dev environment whenever possible. When the software does
something really cool, I let them see that I think it's really cool. Often
they think it's really cool too - and if they thought of it to satisfy a
rather standard business requirement, they're often happy to tell me about
their thought processes and how they came up with the idea, and from THOSE
conversations I gain a wealth of helpful knowledge. Not just about them,
but about the software, the business, the users, etc.
Anne
On Wed, Apr 3, 2013 at 9:01 PM, Keith Hood <klhra -at- yahoo -dot- com> wrote:
> Jessica, you said "It helps, of course, to bother them as little as
> possible and to ask the smartest questions you can." It's been my
> experience the second part of that sentence is the critical point.
> Software developers have a very strong tendency to consider themselves a
> technical and intellectual elite. It is very common for them to refuse to
> make time for other people because they feel those other people somehow
> don't measure up. They easily develop the attitude that they shouldn't
> waste their time with people who don't know as much as they do, because
> they're afraid they'll get trapped into having to spend a lot of time
> giving baby-talk explanations.
>
> It can be crucial for tech writers working in software projects to get
> training in software development, and software QA. That can make a world
> of difference in relations with the people you have to go to for
> information.
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> From our sponsor Doc-to-Help: Want to see a Doc-To-Help web-based Help
> sample with DISQUS for user commenting?
>
> Learn more: http://bit.ly/13xpg5n
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> You are currently subscribed to TECHWR-L as arobotti -at- gmail -dot- com -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
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>From our sponsor Doc-to-Help: Want to see a Doc-To-Help web-based Help sample with DISQUS for user commenting?