Re: Career questions: databases
Date: Sun, 01 Jul 2007 19:51:44 GMT
Message-ID: <jBThi.43001$5j1.41181_at_newssvr21.news.prodigy.net>
Not to pound this into the ground, but I think, with any technology, there are various aspects of the technology that one could be proficient in without being proficient in all aspects of the technology. (Perhaps one could postulate that being proficient in all or nearly all aspects of a technology might be a definition of being "expert").
"DA Morgan" <damorgan_at_psoug.org> wrote in message
news:1183301545.936378_at_bubbleator.drizzle.com...
> Neil wrote:
>> While agreeing with your point about resume fluff, in all fairness, the
>> person claimed he was "proficient" in those technologies, not "expert" in
>> them. At what point does one become "proficient"? That's a good question.
>> But I don't think one needs to be able to field live questions from an
>> audience of developers in order to call oneself "proficient."
>>
>> Neil
>
> I appreciate that but to me proficiency has a higher standard than,
> perhaps, for you. Would you call a DBA that writes shell scripts to
> back up 10g database proficient? I wouldn't.
>
> To quote:
> http://www.thefreedictionary.com/proficient
>
> pro·ficient·ly adv.
> Synonyms: proficient, adept, skilled, skillful, expert
> These adjectives mean having or showing knowledge, ability, or skill, as
> in a profession or field of study. Proficient implies an advanced degree
> of competence acquired through training:
>
> Note: "advanced degree of competence acquired through training"
> --
> 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 Sun Jul 01 2007 - 21:51:44 CEST