gazzag wrote:
> DA Morgan wrote:
>
>> I'm not saying there are no organizations with thinking so muddled but a
>> metalink administrator can create and drop access accounts on-the-fly.
>>
>> If I have someone working on a project what do I gain by saying "here is
>> access to my data and databases but I am going to deny you access to a
>> valuable resource until you've been here 6 months and proven you don't
>> need it."
>>
>> Does anyone work in a shop that thinks this way? I'm interested.
>> --
>> Daniel A. Morgan
>
> As a contractor, I've worked for plenty of organisations, and these
> people, sadly, exist. In my experience, they tend to be the least
> technically competent people who perceive anyone with more knowledge
> than them as a threat. I suspect that he's withholding Metalink access
> as some kind of method of deliberately putting the OP at some kind of
> disadvantage. Sad to say, but true, a lot of people I've worked with
> work for themselves before the organisation. That is to say, they care
> more for their own image within the organisation than actually working
> to give the organisation the best solutions possible.
>
> I once worked at a place where the Unix Sys Admin (not entirely unlike
> Comic Store Guy in the Simpsons) deliberately avoided installing the
> "man" pages on any of the servers to "save space". Personally, I think
> he did it so he could often be seen by the management to appear to be
> the fount of knowledge within the department. Strangely, the "man"
> pages were installed on his own test server ;-)
Remarkable. On reflection I can remember back to before I had my own
metalink account and was in the same situation. I resolved it at the
time by making a metalink account part of my contract before I took a
job. It has been a very long time. Thanks.
--
Daniel A. Morgan
University of Washington
damorgan_at_x.washington.edu
(replace x with u to respond)
Puget Sound Oracle Users Group
www.psoug.org
Received on Fri Aug 18 2006 - 11:09:31 CDT
