[150750] in North American Network Operators' Group
Re: Programmers with network engineering skills
daemon@ATHENA.MIT.EDU (Keegan Holley)
Fri Mar 2 17:46:55 2012
In-Reply-To: <m2fwdqwrzr.wl%randy@psg.com>
From: Keegan Holley <keegan.holley@sungard.com>
Date: Fri, 2 Mar 2012 17:45:18 -0500
To: Randy Bush <randy@psg.com>
Cc: NANOG <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
2012/3/2 Randy Bush <randy@psg.com>
> > In my experience the path of least resistance is to get a junior
> > network engineer and mentor he/she into improving his/hers programming
> > skills than go the other way around.
>
> and then the organization pays forever to maintain the crap code while
> the kiddie learned to program. right. brilliant.
>
> +1 Although, I've seen the opposite where a brilliant developer writes
wonderful code, leaves and you are left with a similarly difficult
situation since there are no more programmers in the department and no
brilliant developers willing to do programming that requires in depth
knowledge of networking.
> Always code as if the guy who ends up maintaining your code will be a
> violent psychopath who knows where you live. -- Martin Golding
>
> randy
>
>
>
