I'm getting into networking (currently studying for the CCNA) and I'm wondering what language(s) would be good to learn.
Let me clarify. I don't plan on getting into programming full-time or even on the side; I'm more interested in learning something to make my job applications look more impressive. While the network administration job market isn't as over-saturated as that of /prog/ramming, it's still not ideal. I want to have an edge over the competition.
With all of this in mind, please suggest something that employers looking for a network administrator would like too see (and perhaps have a use for), not something you personally think is the best due to its good syntax or garbage collection or whatever other qualities you look at when determining whether a language is ``good'' or not.
Basically, a ``sellable'' language rather than a useful one.
Name:
Anonymous2010-11-02 23:52
[aa]> too see
to*[/a]
Name:
Anonymous2010-11-02 23:53
too see to* let's try this again, shell we?
Name:
Anonymous2010-11-02 23:54
shall*
Fuck, I can't type today. But despite my typos, I'd appreciate it if you could make a suggestion.
>>5 Really? Keep in mind I don't know any of the ``in'' jokes here so I can't tell whether you're serious or not. >>6 >>7 >>8 Is that your way of saying you don't know enough in order to make an informed decision?
Also, I hope you're aware that sage is not a weapon, and is pretty much useless when used on a thread that's already at the top of thread list.
Name:
Anonymous2010-11-03 1:13
>>9
You asked for a ``sellable'' langauge, management don't know that it's useless for your position; when they hear Java, they think it means, 'SERIOUS PROGRAMMING KNOWLEDGE'.
>>11
Seriously? That's almost Java level retardation.
Name:
Anonymous2010-11-03 5:19
>>1
If I were hiring a network administrator, I wouldn't ask for any programming other than knowledge of the UNIX shell (shell so-called scripts) and whatever he'll be managing. I'd value Python in case he needs to build some tool to do something. I wouldn't value Java as it's not useful for network administration.
I'd require GNU/Linux wizardry, though. Focus on that.
>>15
Scala, hands down. Though a network admin needs Scala as much as a truck driver needs a palm tree.
Name:
Anonymous2010-11-03 7:39
>>13 I'm good with shellscripts and general GNU/Linux tomfoolery. I'm very familiar with all the ``enterprise'' distros used in corporate environments (Red Hat, CentOS, and openSUSE).
I am aware that programming knowledge isn't top priority for someone like me, but as I said, I want to do whatever I can to make my applications stand out. Skills that aren't entirely relevant can still be helpful.
For example, I have no criminal record, lots of volunteer work under my belt, and up-to-date CompTIA certifications that aren't really related to networking. Does any of that make me a better potential network administrator? Not really. Will it make my applications look at least a little more appealing? Definitely. However, despite these things I have already, there's much more I can do to help it even further. These things shouldn't take precedence over my networking skills, but they make for good additions. >>14
I'm actually planning on learning Japanese next semester since I'll be studying abroad there in the summer and perhaps the fall semester as well. And no, I'm not a weeaboo. I tried Mandarin for a while, but I found learning the phonology to be quite a hassle. And as someone who generally doesn't speak with much tonal variation, I'd probably be bad with speaking the language even if I stuck with learning it further. I know Japanese has its own challenges too, but I'd still prefer it over Mandarin.
>>16
>> Which is more sellable, F# or Scala? Scala, hands down.
What makes you think so?
CIL-based .Net is better than archaic JVM in so many ways, plus F# is supported my MSVS, which is also somewhat better than Eclipse, the only sane choice for Scala.
For personal projects you can choose whatever you like, but in enterprise, the choice is made based on a completely different set of criteria.
VBScript is the go-to automation language for the discerning administrator.
As a bonus it qualifies you to work on a wide range of legacy ASP applications.
Why can't you guys agree on something? Is it really that hard or complex? You all seem to have different preferences and opinions.
I guess I just naïvely thought it might be a little easier to find something suitable for what I'm describing. As in, I expected replies like ``try language x, it's great for networking-related tasks'' or ``most employers would really like to see language y''.
>>31 I expected replies like ``try language x, it's great for networking-related tasks''
Why would you expect that when you explicitly specified that you weren't interested in that aspect?
Name:
Anonymous2010-11-03 12:59
>>1
12 years of sysadmining experiencing here, also studying for his Cisco certs.
- You will need Perl, period. There is no discussion about it. Ignore the other faggots on this board who say otherwise. You need to know Perl for when Bash and IOS aren't enough.
- Previous poster said Linux/UNIX wizardry. Very yes. An important part of this is knowing shell scripting inside and out.
- The ability to read and fix C code is very useful as well.
- One of the easy hipster OOP languages like Python and/or Ruby would be good to know as well. Python though I detest it does have more modules available.