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.
> I would cast "migrate" into the same pit as "transition."
>
> > -----Original Message-----
> > From: Combs, Richard
> > Sent: Wednesday, November 04, 2009 5:13 PM
> > To: Dan Goldstein; techwr-l -at- lists -dot- techwr-l -dot- com
> > Subject: RE: Transition that verb out of here!
> >
> > You're right -- I was focused on your catchy subject line and
> > read the actual quote too carelessly. There are plenty of
> > decent, upstanding transitive verbs they could have used --
> > "change," switch," "migrate"
> > ...
I find "transition" used as STC (and so many politicians and biz-baffle-speakers) used it to be jarring and of no advantage.
"Migrate", on the other hand works and feels right in either mode, depending on context.
In my niche, it is common to "migrate" one's encryption and signing keys, one's certificates, and other cryptographic finery to newer-generation (or competing...) systems. In that context, "migrate" carries implications beyond "transfer". It's possible to "transfer" them many places, and in many ways that they will definitely arrive, but they probably won't be usable.
Similarly, I could "transfer" a big, complicated database from one computer or network to another, but if I didn't have the right "machinery" in place, all I'd have is a big blob of files that I couldn't use. Migrating a large database has implications beyond "chop here and here, and ftp the pieces over to here".
Same again for users on one network going to a different or updated network... though that might be just another example of a database migration, I suppose.
To me and to the people in this industry, transfer (and some similar verbs) implies "shift location", while migrate implies "relocate with all your amenities re-installed and configured the way you like 'em, and a fresh pot of coffee brewing when you come in the door".
Ducks migrate and set up their own housekeeping at the new digs.
Data migrates, but not on its own. Especially for special-format, special-use data, you have to hold its hand and "migrate it", and know whether to place a mint or a rose on the pillow...
If there's a better word or a better way of saying it that doesn't annoy or add cost, I'm all ears. :-)
- Kevin
The information contained in this electronic mail transmission
may be privileged and confidential, and therefore, protected
from disclosure. If you have received this communication in
error, please notify us immediately by replying to this
message and deleting it from your computer without copying
or disclosing it.
Are you looking for one documentation tool that does it all? Author,
build, test, and publish your Help files with just one easy-to-use tool.
Try the latest Doc-To-Help 2009 v3 risk-free for 30-days at: http://www.doctohelp.com/
Help & Manual 5: The complete help authoring tool for individual
authors and teams. Professional power, intuitive interface. Write
once, publish to 8 formats. Multi-user authoring and version control! http://www.helpandmanual.com/
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
