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: Using "Fences" as File Management Tool? From:Emoto <emoto1 -at- gmail -dot- com> Date:Wed, 1 Nov 2017 13:34:03 -0400
On Wed, Nov 1, 2017 at 11:35 AM, Chris Morton <salt -dot- morton -at- gmail -dot- com> wrote:
> *Trouble ahead, trouble behind,*
> *And you know this notion...just crossed my mind.*
>
> Greg's points are critical here. If a compromise can be struck in relation
> to where the actual files are stored, great.
>
> If not, then I might be inclined to use the SysAdmin as the bad cop,
> asserting that Fences only serves as another layer of user insulation that
> runs counter to accepted system and file backup procedures.
I'll be revisiting this, probably later today. I will go for the combo
deal of letting her use Fences for shortcuts to files, but make the
files themselves live in a structure that I will create for her, just
to get it done.
> Yours is a Windows environment. If the new hire doesn't care to fully
> understand the OS and its file structure, then I'd question her ability to
> be adaptive to the established ways of the company.
>
> I worked at several places in the past where one was simply NOT permitted
> to introduce software to one's own system, period. Other places were a bit
> more lenient, but I'd need to first seek permission to use such things as
> favored utilities the company did not yet know about (but enhanced
> productivity).
I don't know if it was approved or not. I don't care much about that, frankly.
> I don't know what the nOOb will be documenting, but this entire thread
> would give me pause regarding whether or not she's an appropriate fit.
There are certainly questions along those lines, however, the subject
matter of the medical device instructions being worked on is not
something foreign to this person, so that is a point in her favor, to
some extent.
> I may be a bit hard-nosed about this, but it's already sounding problematic
> when the easiest solution is to learn the file system. In this regard, what
> is so bloody complicated about understanding folders and subfolders,
> drawers and cabinets when related to such physical items in the paper-based
> world?
Frankly, I was baffled to get pushback on that. Last thing I expected.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Visit TechWhirl for the latest on content technology, content strategy and content development | http://techwhirl.com