Should Software Engineers Seek CCNA's?
kernel2 asks: "I'm in the software engineering profession and some of my friends are about to enroll on a CCNA (Cisco Certified Network Administrator) course and are egging me on to join as well. I'm trying to decide whether I should do the course or not. On the one hand it might help me understand networking (especially in bigger corps) better and that is something I love (networking). It might also help me diversify and improve my chances of landing a job in these strained and difficult times (and that's primarily why my friends are doing it). But wouldn't it look odd on my CV? I mean why would someone highly interested in software (with a Software Engineering degree) do CCNA?"
Not every programmer has a myopic world view, and I think that the ones who can think broadly are the ones who succeed most often. Take a look at Larry Wall's background for an idea of what a diverse background can produce.
Why can't I moderate something "Wrong" or at least "Grossly Misinformed"?
Cisco Certified people get the top dollars in the industry. Their top-notch certification (CCNP, I believe, for Network Professional, but I might be wrong) easily fetches $80K+ around the United States and $100K+ in big cities. That's not pocket change.
Cisco Certified people, assuming you're through with the certification and actually get it (dropout rate is quite high, lots of hard-working hours must be invested), you're sitting on the money bag.
For example, in Ukraine a Cisco certified expert gets a paycheck of $25K yearly. That's Ukraine, where the average salary is $200 and anyone in software development is expected to make $500-700 max. The catch? Only 13 Cisco-certified experts (their top certificate) for entire freaking country of 50 mil. people.
If you have a chance to get free education, go for it.
On a whim, I took a COBOL class in college (1989). I learned one critical fact during that class - that I *never* wanted to do COBOL programming again.
It never showed up on my resume, and very few people know about it.
However, I passed up on some $20k/year salary increases by *not* listing it on my resume during the late 1990s. It was a conscious choice - and one that I was glad to be able to make.
By adding networking to your skill set, you could become the IT person at a small company. Imagine being the fifteenth guy to work for Microsoft, for example. Big bucks.
More opportunities (if you like doing that work still, once the class is over), or knowledge that you want to avoid the field like it was the plague. Hmmm. . .
Chivalry is not dead, it's just frequently misspelt. - M. Langley
CCNA stands for Cisco Certified Network Associate not Administrator. There's a big difference.
Sure the CCNA course has lots of cisco specific syntax - but you can't know the syntax without learning the theory - which by the very nature of TCP/IP must be universal. VLSM and subnet masking is the same in Cisco land, *nix or M$.
Same goes with RIP & OSPF - true tho - there is a bit of cisco proprietry routing such as IGRP & EIGRP, but the emphasis is more on RIP and OSPF.
when learning networking I believe its useful to actually impliment the theory. Choosing to do so on Cisco routers, or Linux or Windows is irrlevent. I'd suggest that once you've done the CCNA course then you should hunt down some other routers and switch gear and try to impliment using different syntax. Linux is a good choice for the routing stuff (for RIP anyway - not sure about OSPF).
cavet - I teach in the Cisco Network Academy CCNA programme