I have interest in computer networking, but every time i visit the programming or computer section of Nairaland all i see is PROGRAMMERS.

I think computer networking needs a section of its own, where experts can help newbies like me on Cisco certifications and other ICT certifications. I'm sure we have even CCIEs on nairaland

What do you people think?

we are managing the career section. post whatever u want to post there.

ebixy:
I have interest in computer networking, but every time i visit the programming or computer section of Nairaland all i see is PROGRAMMERS.

I think computer networking needs a section of its own, where experts can help newbies like me on Cisco certifications and other ICT certifications. I'm sure we have even CCIEs on nairaland

What do you people think?

what do you wana know?

It is too small a world to get a separate section

Dpredictor:


what do you wana know?

What it feels like to work as a network admin i.e what the job routines are like

Handling real life challenges with router and server failures and the pressure that comes with being a step ahead of hackers or intruders.
The TV series MR ROBOT gave me an idea of that feels like but i would like to hear it from the Nigerian perspective.

I know networks engineers earn a lot but you hardly see job advertisement from big companies, is their employment based on recommendations or? Considering the kind of job requires trust because you would be dealing with many sensitive things

Qudbell:
we are managing the career section. post whatever u want to post there.

Thank you.

Do Network Engineers have someone to look up to? Like programmers can look up to the creators of their various programming languages or programmers that have made global impact e.g Bill Gates

When i have more questions I would quote you

Computer networking is covered under Network or Socket Programming so you can drop your post here too and we programmers can help you.

Febup:
Computer networking is covered under Network or Socket Programming so you can drop your post here too and we programmers can help you.

No ... No... No... Hell no!!
Programmers know little about networking.... Now that said, I believe programmers actually know the some stuff... Which is mostly concerning the uppermost 3 or 4 components of the OSI networking model....

A Server infrastructure Programmers may be a domain expert within the Application, Presentation and Session layers... The Network Engineer should be at least very familiar with the Physical Bit, Data link, and Network layers. There may be a good deal of overlap in the transport layer.

------------------------------
Simply knowing IP, cabling, etc shouldn't qualify anyone to call himself a Network Engineer in my purview.

I claim very little knowledge on Networking; so take me with a grain of salt
(Image: courtesy of lifewire)

ebixy:


Thank you.

Do Network Engineers have someone to look up to? Like programmers can look up to the creators of their various programming languages or programmers that have made global impact e.g Bill Gates

When i have more questions I would quote you

looking at both terms - network engineers and programmers, the "real" work lies at the programming level which explains why they are more pronounced, its a complex field to talk about. the reason network engrs dont make global impact is because they dont really make innovations, brainstorming ideas in that regard; all they do is create, maintain, troubleshoot and manipulate how data is transferred within the network either from the router end or from the node (PC or server) end. they arent really building something we can see and the network we are talking about is an abstract term. but programmers have the opportunity to create groundbreaking innovations like facebook (Zuckerberg), microsoft (gates) etc. which explains why they make global impact. hope it answers your question. I stand to be corrected.

WhiZTiM:


No ... No... No... Hell no!!
Programmers know little about networking.... Now that said, I believe programmers actually know the some stuff... Which is mostly concerning the uppermost 3 or 4 components of the OSI networking model....

The OSI networking model were created by programmers. Networking Devices all have an Operating System written by programmers which are the backbone of all Computer Networking. Read an account from someone that worked at CISCO: I worked at Cisco for an year. In that time period I worked on the product which had the core OS written in C. Backend (on top of OS) was written in C++, XML, Perl, Bash etc. Desktop front end in Java. Web front end in HTML, CSS, Javascript. For my work I even used Python (apart from above languages). And of course the QEs used Tcl, Expect etc. Source: https://www.quora.com/What-is-the-most-widely-used-programming-language-at-Cisco

The name Tcl is derived from "Tool Command Language" and is pronounced "tickle". Tcl is a radically simple open-source interpreted programming language that provides common facilities such as variables, procedures, and control structures as well as many useful features that are not found in any other major language. Source: https://en.wikibooks.org/wiki/Tcl_Programming/Introduction

@Fepub Hmmn... there's no point going back and forth this. ...case closed.

So, how many times do programmers get to deal with the many routing protocols that tie computer nodes on THE INTERNET, LAN and WAN.

OSPF, BGP,TCP/IP,RIP,VPN,RSTP,EIGRP,VOIP etc

Like somebody said, network engineers rarely create new things. In fact the only reason you would need a network engineer is when you need to work in an environment where terminals are tied together and need to share information.

Contrary to what someone mentioned, the networking world has a vast space of field to conquer. It's more challenging and takes years and years to actually master (i am not talking of paper certification).

While the programmer has all he or she needs, packed in the laptop, the network engineer requires thousands of dollars to setup a CISCO or JUNIPER lab for a CCIE or a JNCIS-SP exam.

In short, the Network engineers man the internet, while programmers make the internet more exciting.

Financially, the programmer stands a better chance of making a million dollar at 18 years while a network engineer might have just years of career and tons of certifications to show for years of commitment.

Its sad really

persius555:
So, how many times do programmers get to deal with the many routing protocols that tie computer nodes on THE INTERNET, LAN and WAN.

OSPF, BGP,TCP/IP,RIP,VPN,RSTP,EIGRP,VOIP etc

Like somebody said, network engineers rarely create new things. In fact the only reason you would need a network engineer is when you need to work in an environment where terminals are tied together and need to share information.

Contrary to what someone mentioned, the networking world has a vast space of field to conquer. It's more challenging and takes years and years to actually master (i am not talking of paper certification).

While the programmer has all he or she needs, packed in the laptop, the network engineer requires thousands of dollars to setup a CISCO or JUNIPER lab for a CCIE or a JNCIS-SP exam.

In short, the Network engineers man the internet, while programmers make the internet more exciting.

Financially, the programmer stands a better chance of making a million dollar at 18 years while a network engineer might have just years of career and tons of certifications to show for years of commitment.

Network Engineer here....And I love my work to bits!!! Open and ready to answer any and all questions

Yooku:
Network Engineer here....And I love my work to bits!!! Open and ready to answer any and all questions

How 'easy' was it getting your first job with probably no experience

WhiZTiM:


No ... No... No... Hell no!!
Programmers know little about networking.... Now that said, I believe programmers actually know the some stuff... Which is mostly concerning the uppermost 3 or 4 components of the OSI networking model....

A Server infrastructure Programmers may be a domain expert within the Application, Presentation and Session layers... The Network Engineer should be at least very familiar with the Physical Bit, Data link, and Network layers. There may be a good deal of overlap in the transport layer.

------------------------------
Simply knowing IP, cabling, etc shouldn't qualify anyone to call himself a Network Engineer in my purview.

I claim very little knowledge on Networking; so take me with a grain of salt
(Image: courtesy of lifewire)

To say that programmers know very little about Networking is a very broad generalisation.

What kind of programmers are your referring to? Those that build server side applications have to know a little about Networking as they must understand port numbers/TCP sockets.

When developing applications for Malware, you do have to understand networking to a certain extent.

I know what you are trying to say, in that most programmers know little about Networking, but you can not generalise. There are some people out there that have a knack for studying anything computing oriented.

persius555:
So, how many times do programmers get to deal with the many routing protocols that tie computer nodes on THE INTERNET, LAN and WAN.

OSPF, BGP,TCP/IP,RIP,VPN,RSTP,EIGRP,VOIP etc

Like somebody said, network engineers rarely create new things. In fact the only reason you would need a network engineer is when you need to work in an environment where terminals are tied together and need to share information.

Contrary to what someone mentioned, the networking world has a vast space of field to conquer. It's more challenging and takes years and years to actually master (i am not talking of paper certification).

While the programmer has all he or she needs, packed in the laptop, the network engineer requires thousands of dollars to setup a CISCO or JUNIPER lab for a CCIE or a JNCIS-SP exam.

In short, the Network engineers man the internet, while programmers make the internet more exciting.

Financially, the programmer stands a better chance of making a million dollar at 18 years while a network engineer might have just years of career and tons of certifications to show for years of commitment.

More than you would imagine if the programmers job is to write the software for the routers and switches you are referring you.

You are not looking at things from an abstract level. You are seeing things from the surface only. Who designs the software for Cisco iOS routers/switches, Cisco NX-OS routers /switches, etc.

I am aware that programming is not Computer science but it is a small part of it, just like computer networking. Djikstra's algorithm for instance is pure graph theory. This same graph theory is applied to OSPF routing protocol.

ebixy:

How 'easy' was it getting your first job with probably no experience

After graduating from Univ in June, I went straight into intensive self study and preparation for the CCNA certificate and passed the exam in October. Prior to this I had interviewed with an ISP to do my national service with them and told them I was on preps for the CCNA so they were very interested in taking me on. By the time I started national service in December, having the CCNA under my belt put me at a skill level which was higher than some of the engineers already in the company. I guess although I didn't have any job experience the skill set and drive to learn made them take me on and eventually offer me a full time role in the company after national service had come to an end. So I guess I had no experience, but I was highly skilled. That's one way to get your foot in the door. Get the certification to demonstrate that in terms of knowledge you are there. You do not need much training and you can hit the ground running once you are given the chance to come on board..

Fulaman198:


More than you would imagine if the programmers job is to write the software for the routers and switches you are referring you.

You are not looking at things from an abstract level. You are seeing things from the surface only. Who designs the software for Cisco iOS routers/switches, Cisco NX-OS routers /switches, etc.

I am aware that programming is not Computer science but it is a small part of it, just like computer networking. Djikstra's algorithm for instance is pure graph theory. This same graph theory is applied to OSPF routing protocol.

Man,the guys who write the software code for the networking devices are some really smart people. They have to be able to understand the protocols inside out to be able to churn out those lines of code which eventually comes out as IOS/NX-OS/JUNOS etc. I will give them their due respect any day.

Yooku:


After graduating from Univ in June, I went straight into intensive self study and preparation for the CCNA certificate and passed the exam in October. Prior to this I had interviewed with an ISP to do my national service with them and told them I was on preps for the CCNA so they were very interested in taking me on. By the time I started national service in December, having the CCNA under my belt put me at a skill level which was higher than some of the engineers already in the company. I guess although I didn't have any job experience the skill set and drive to learn made them take me on and eventually offer me a full time role in the company after national service had come to an end. So I guess I had no experience, but I was highly skilled. That's one way to get your foot in the door. Get the certification to demonstrate that in terms of knowledge you are there. You do not need much training and you can hit the ground running once you are given the chance to come on board..

Quiet motivating, thanks for sharing your story. I'm on that path of intensive self development. I want to specialize in Security/Cyber Security

Yooku:


After graduating from Univ in June, I went straight into intensive self study and preparation for the CCNA certificate and passed the exam in October. Prior to this I had interviewed with an ISP to do my national service with them and told them I was on preps for the CCNA so they were very interested in taking me on. By the time I started national service in December, having the CCNA under my belt put me at a skill level which was higher than some of the engineers already in the company. I guess although I didn't have any job experience the skill set and drive to learn made them take me on and eventually offer me a full time role in the company after national service had come to an end. So I guess I had no experience, but I was highly skilled. That's one way to get your foot in the door. Get the certification to demonstrate that in terms of knowledge you are there. You do not need much training and you can hit the ground running once you are given the chance to come on board..

What did you graduate in if you do not mind me asking?

Fulaman198:


What did you graduate in if you do not mind me asking?

Electrical Engineering....To be honest I would have opted for a different course if I had the opportunity. It didn't really cut it for me as most of the content was power engineering & electonics and the likes. I was more into IT long before University. It's only in the last couple of years that Bachelors Degrees in IT have become popular. I discovered networking in my 2nd year at a seminar organized by some guys who were setting up the NOC for our Univ and that's where I got really interested. Been an exciting journey since then!!

Yooku:


Electrical Engineering....To be honest I would have opted for a different course if I had the opportunity. It didn't really cut it for me as most of the content was power engineering & electonics and the likes. I was more into IT long before University. It's only in the last couple of years that Bachelors Degrees in IT have become popular. I discovered networking in my 2nd year at a seminar organized by some guys who were setting up the NOC for our Univ and that's where I got really interested. Been an exciting journey since then!!

Great, I'm glad that you are enjoying it. Electrical Engineering is not a bad read by the way.

Yooku:


Electrical Engineering....To be honest I would have opted for a different course if I had the opportunity. It didn't really cut it for me as most of the content was power engineering & electonics and the likes. I was more into IT long before University. It's only in the last couple of years that Bachelors Degrees in IT have become popular. I discovered networking in my 2nd year at a seminar organized by some guys who were setting up the NOC for our Univ and that's where I got really interested. Been an exciting journey since then!!

I sent you a pm sir. pls reply. i have some questions 2 ask u.

I see lot of awful comment in here, for those of you that call yourself a programmer, its because you pick up a book on the language then you think you already know all about the language, its funny.
If you are real interested in learning networking pick up:
1) Andrews Tanenbaum Computer Networks Textbook for a start then migrate to
2) Richards Stevens Tcp/Ip Illustrated text volume 1 - 3, immerse yourself in the knowledge, though we now have update on the text, Later move on to the Programming aspects: Volume 1 should do.
3) Unix Network Programming, for real examples on networking
Later on start your journey with that basis and move to the certification aspect
CCNA and co.

Advanced Programmer know all about computer either Network or wortnek
Thanks

Bahat:
I see lot of awful comment in here, for those of you that call yourself a programmer, its because you pick up a book on the language then you think you already know all about the language, its funny.
If you are real interested in learning networking pick up:
1) Andrews Tanenbaum Computer Networks Textbook for a start then migrate to
2) Richards Stevens Tcp/Ip Illustrated text volume 1 - 3, immerse yourself in the knowledge, though we now have update on the text, Later move on to the Programming aspects: Volume 1 should do.
3) Unix Network Programming, for real examples on networking
Later on start your journey with that basis and move to the certification aspect
CCNA and co.

Advanced Programmer know all about computer either Network or wortnek
Thanks

I completely agree with your comments.

#1 is a great book, I have his book for Operating Systems which I used back in my Undergrad years about a decade ago. He (Tanebaum) writes very good books.

#3 is also very good. I do agree with you that to be a great programmer understanding Networking helps a lot. But to be honest, even in the "advanced" countries like the United States, you will find people with Computer Science backgrounds that can code, but do not understand Computer networking.

I think it is important to know both.

Fulaman198:


I completely agree with your comments.

#1 is a great book, I have his book for Operating Systems which I used back in my Undergrad years about a decade ago. He (Tanebaum) writes very good books.

#3 is also very good. I do agree with you that to be a great programmer understanding Networking helps a lot. But to be honest, even in the "advanced" countries like the United States, you will find people with Computer Science backgrounds that can code, but do not understand Computer networking.

I think it is important to know both.

WAddup bro

CAMNEWTON4PRES:


WAddup bro

Hey what's up man it has been a long time. What have you been up to?

Fulaman198:


Hey what's up man it has been a long time. What have you been up to?

school things & becoming a young professional/adult

CAMNEWTON4PRES:


WAddup bro

Hey You.

Fulaman198:


Great, I'm glad that you are enjoying it. Electrical Engineering is not a bad read by the way.

Be still my beating heart. Long time no see Mr. Toes.