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.
Persistence is new, the methods to use persistence are new, and the full
usage of the terms that developers use to describe their methods to use
persistence are new. Developers are already using the concept and words "to
persist data" and writers writing for them should use the terms that
developers use.
Perhaps writers would like the ability to correct all of the developer
resources on their word usage, but developer documentation should reflect
the work of developers and not the language that the writer wants to use.
Microsoft has no problem using "to persist" in its developer documentation.
I think that the biggest problem in the use of "to persist" comes from rigid
thinking writers that obsess over word usage because they do not understand
the language of developers.
Technical writers do not document conversational language, they document the
language of technology. I think that it is a waste of time and energy to
confuse the two languages because they share words and then try to impose
conversational language onto technology. Technology and its language
evolves very fast. Isn't it better to be current with the language of
technology than to resist its evolution?
Fuddy duddies don't like change. Technical writers should be as dynamic and
evolutionary as the world they document. Teehee.
Lauren
> -----Original Message-----
> From: techwr-l-bounces+lt34=csus -dot- edu -at- lists -dot- techwr-l -dot- com
> [mailto:techwr-l-bounces+lt34=csus -dot- edu -at- lists -dot- techwr-l -dot- com] On
> Behalf Of iFaqeer (SIA)
> Sent: Monday, June 04, 2007 6:43 PM
> To: techwr-l -at- lists -dot- techwr-l -dot- com
> Subject: Re: "to persist data"
>
> Just read the IBM page. It doesn't seem to imply the "to
> persist data" usage:
>
> persist
> To be maintained across session boundaries, usually in nonvolatile
> storage such as a database system or a directory.
> persistence
> (1) A characteristic of data that is maintained across session
> boundaries, or of an object that continues to exist after the
> execution of the program or process that created it, usually in
> nonvolatile storage such as a database system.
> (2) In J2EE, the protocol for transferring the state of an entity
> bean between its instance variables and an underlying database. (Sun)
> persistent
> Pertaining to data that is maintained across session boundaries,
> usually in nonvolatile storage such as a database system or a
> directory.
>
> I say we write around it as long as we can--and hope it is a
> passing fad ;)
>
> You know, something like "store it as persistent data" or "store it in
> persistent form/configuration" etc.
>
> When it passes into the language (like "automation", "online", and so
> on) or, importantly, the specific accepted usage of the domain one is
> operating in, we can get with the program.
>
> My tuppence 'orth,
>
> SIA
> --
> [Sabahat Iqbal Ashraf]
> -----------------------------------
> New project I am contributing to:
>http://www.UnderstandingPakistan.com
> -----------------------------------
> Cell: (510) 304 5927
> Web: http://iFaqeer.wikispaces.com/
> Blog & Podcast: http://iFaqeer.blogspot.com or
>http://pkblogs.com/iFaqeer
> Urdu Podcast: http://AzadKarachiRadio.blogspot.com or
>http://pkblogs.com/AzadKarachiRadio
> -----------------------------------
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> 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 lt34 -at- csus -dot- edu -dot-
>
> To unsubscribe send a blank email to
> techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
> or visit
>http://lists.techwr-l.com/mailman/options/techwr-l/lt34%40csus.edu
>
>
> To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com
>
> Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
>http://www.techwr-l.com/ for more resources and info.
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-
