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: The Mythical Man-Month From:<neilson -at- windstream -dot- net> To:Richard Lewis <tech44writer -at- yahoo -dot- com>, Techwr-l <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Tue, 19 Jun 2007 18:14:08 -0400
> neilson wrote:
>
>> The key is to focus on the user view and not on the technology. This
>> paradigm even applies for products that are for very technical users,
>> in my opinion.
>
> Richard Lewis responded:
>
> Right on! I still do not get why this is so hard for so many business
> analysts - let alone developers. I mean - this is supposed to be their
> job. Any insights as to why most BA's have such a hard time maintaining
> a user view?
Yes. Clutter. Once you know too much about something it is hard to step
away and see less of it. Creating OO abstractions is not sufficient,
because they are still within the technology framework. Any time that
implementation is put ahead of design, or design ahead of requirements,
the wrong minds are in control. For small projects there may be no bad
consequences, because the team is small and flexible. Any time you go
beyond one or two guys in a garage you have to be able to communicate
the requirements and the design to the rest of the team. Even one
developer alone has to listen to the intended customer.
Sometimes the clutter that drives the project is existing or owned
technology. "We shall build the new server on our established code,
because reuse is good and because we spent too much on developing it
in the first place." Sounds brilliant, unless you're making wine: "We
shall add one liter of this costly but sour and undrinkable plonk to
each 29 liters of our excellent wine, so that we do not waste the
money and hard work that we poured into making it."
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-