[124550] in North American Network Operators' Group
Re: Finding content in your job title
daemon@ATHENA.MIT.EDU (Jimi Thompson)
Fri Apr 2 10:20:58 2010
Date: Fri, 02 Apr 2010 09:20:05 -0500
From: Jimi Thompson <jimi.thompson@gmail.com>
To: Jorge Amodio <jmamodio@gmail.com>,
Jeroen van Aart <jeroen@mompl.net>
In-Reply-To: <v2x202705b1003311814sd411ae26n402144bc7453c587@mail.gmail.com>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On 3/31/10 8:14 PM, "Jorge Amodio" <jmamodio@gmail.com> wrote:
>> I agree with the misuse of the term "Engineer" in IT. I think it should only
>> be used for the "official" protected title of civil engineer. Which I
>> believe is a very respectable job. Sad but true, in IT too many people have
>> some form of engineer in their job title but are almost totally clueless.
>
> [ X-Operational_Content = 0 ]
>
> Can't resist.
>
> When I read your message it brought back to my memory a nice guy that
> used to work for me eons ago, very clever, smart and hands-on, he had
> a Bachelor's Degree in Psychology.
>
> One day, we had some sort of outage and I found him in the "computer
> room" sitting in front of one of the racks with some routing gear, I
> still have that image in my memory he looked like he was doing some
> sort of group therapy with the routers, I couldn't resist and told him
> "Hey Joey, Freud won't help you, get your butt off of the chair and
> follow the default procedure, power cycle the damn beast".
>
> There were also several folks with various degrees in Physics, experts
> on blowing up stuff.
>
> Again, IMHO, in this field a title may help or may provide others a
> relative idea where you fit in a large organization, or help the HR
> folks know how much to put on your paycheck or what kind of
> benefits/perks go associated with that level, but I still believe that
> substance is more important.
>
> Regards
> Jorge
> COOK
> Chief Old Operations Knucklehead
>
HAH! My self chosen job title is Chief Pest, Annoyer of Developers, and
Destroyer of Misconceptions. All in all, it's fairly accurate. Among other
things I manage a team of developers, I often have to disabuse management of
some silly idea or other, and frequently have to play gladfly to enable
change.
