[150811] in North American Network Operators' Group
Re: Programmers with network engineering skills
daemon@ATHENA.MIT.EDU (Keegan Holley)
Mon Mar 5 15:42:10 2012
In-Reply-To: <36D900B5-A5C3-449D-B6E3-FD2FD4D495DE@delong.com>
From: Keegan Holley <keegan.holley@sungard.com>
Date: Mon, 5 Mar 2012 15:40:26 -0500
To: Owen DeLong <owen@delong.com>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
2012/3/5 Owen DeLong <owen@delong.com>
> Given my experience to date with the assumptions made by programers about
> networking in the following:
>
> Apps (iOS apps, Droid apps, etc.)
> Consumer Electronics
> Microcontrollers
> Home Routers
>
> I have to say that the strategy being used to date, whichever one it is,
> is not working. I will also note that the erroneous assumptions, incorrect
> behaviors, and other problems I have encountered with these items are
> indicative of coders that almost learned networking more than of networkers
> that almost learned software development.
>
>
I think it comes down to economics mostly. Most development jobs either do
not require knowledge of networking or do not enforce the requirement.
There are plenty of jobs where developers do not need to know networking so
when it's a sticking point it just becomes harder to find someone that
fits. This doesn't give the average developer much incentive to learn
networking, even if it leads to buggy or incorrectly written code. On the
other hand a senior net-eng that can code is worth is weight in gold,
especially if he can spit out palatable webUI's for everything.
