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: User Documentation in Agile Development Teams From:Lin Sims <ljsims -dot- ml -at- gmail -dot- com> To:John G <john -at- garisons -dot- com> Date:Mon, 27 Mar 2017 12:43:58 -0400
And yet, those same programmers use software themselves, and have no doubt
cursed the lack of intuitiveness of a LOT of it.
On Mon, Mar 27, 2017 at 12:09 PM, John G <john -at- garisons -dot- com> wrote:
> Many programmers I know loathe and despise users and consider them
> 'wet-ware' ... live beings who exist solely to misuse and break what they
> have so lovingly crafted.
>
> And you wonder why things are the way they are ...
>
>
> My 2Â,
> JG
>
> On Mon, Mar 27, 2017 at 12:05 PM, Monique Semp <monique -dot- semp -at- earthlink -dot- net
> >
> wrote:
>
> > In software development, a problem I've seen far more often is that
> >> developers don't really understand customers' use cases.
> >>
> >
> > Yes, that's correct!! <rant-kvetch>I've worked with many teams at many
> > companies where the engineers in particular don't have any idea how the
> > whole flow will work, what the customers need from the product overall,
> and
> > how the customer will use it. When I talk to the engineers they're often
> > not even troubled by the fact that they don't know. They frequently say
> > things such as, "I'm just implementing the protocol, and donât need to
> know
> > how this code fits into the process." Such thinking certainly explains
> the
> > lack of usability in systems!</rant-kvetch>
> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > Visit TechWhirl for the latest on content technology, content strategy
> and
> > content development | http://techwhirl.com
> >
> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> >
> > You are currently subscribed to TECHWR-L as vwritert -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
> >
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Visit TechWhirl for the latest on content technology, content strategy and
> content development | http://techwhirl.com
>
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> You are currently subscribed to TECHWR-L as ljsims -dot- ml -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
>
--
Lin Sims
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com