🚀 go-pugleaf

Tony Langdon wrote:
> 
> It's 04 Jun 98  05:33:08,
> We'll return to tenderizer@-nospam-infosuper.com and All's
> discussion of ARE YOU MCSE/CNE CERTIFIED.. YET?
> 
>  te> That's very true, but on the other hand, field experience is very
>  te> seldom broad enough to replace book learning.  This business isn't old
>  te> enough for anyone to have seen everything that the MSCE program
>  te> covers.  Either all your experience has been in a single domain
>  te> environment, or you've never had to work with Novell servers, or
>  te> you've never seen a complicated TCP/IP environment, etc.
> 
> Good point.  For me, the most valuable experience I had was _off_ the
> job, at home, where I've played around with several OS's from DOS to NT
> and Linux, and administered Internet services.  Doesn't make any money,
> but a clued up employer will spot these things on a resume.  I wouldn't
> mind a MSCE or CNE alongside, to top it off. :-)

I am one such clued in employer. I don't let MCSE fool me for
a minute. I look for people who have an understanding of the
bigger picture, beyond the trained Microsoft mouse-clicker.
MCSE is not an engineering certification, just a technical
training label. I haven't hired one MCSE yet, and given the
resumes I've seen, probably won't in the near future either.

> And there's also a whole lot to learn about the quirks of real
> networking hardware and software in the field.  NT, Linux, Cisco
> routers, etc all have their quirks. :-)
> 
> . That's fine in practice, it'll never work in theory!

Real networks and systems have their own set of problems
that no amount of Microsoft marketing will make go away :-)