From: Giblin Dean L. (DLGiblin@VASC.com)
Date: Mon Nov 25 2002 - 15:36:45 GMT-3
I would consider a network engineer a person that could support the
company's network infra-structure and interact with the systems that run
over them. For example, I would expect even a network engineer that
works with routers and switches to be able to diagnose and trouble shoot
DHCP, Wins, DNS and other communication, connectivity, and performance
issues. These applications typically reside on a server of some type.
As far as the programming language - a programming language is nothing
but a tool. A tool that is commonly used by network engineers that work
at an enterprise level that are required to maintain several comparable
devices. A programming language provides a cost effective, consistent,
and easy mechanism to perform systematic updates. I would think that
even network engineers that work strictly with routers and switches
would benefit significantly from automating routing tasks on 50+ similar
devices. Once these tools are in place, it is typically a simple matter
to modify the script to change a different variable.
Dean
> From: <FLCCNP@aol.com>
> To: <johntafasi@yahoo.com>; <ccielab@groupstudy.com>
> Sent: Monday, November 25, 2002 11:19 AM
> Subject: Re: Programming Language for Network Engingeers.
>
> > I guess the real question is what do you consider a network
engineer?
> >
> > If you consider a network engineer somebody who deals with routers
and
> > switches, I see no need for the engineer to know any programming
> languages.
> >
> > If you feel he deals with servers too, then it's pretty wide open.
This archive was generated by hypermail 2.1.4 : Tue Dec 03 2002 - 07:23:10 GMT-3