[150608] in North American Network Operators' Group
RE: Programmers with network engineering skills
daemon@ATHENA.MIT.EDU (Jamie Bowden)
Tue Feb 28 11:29:18 2012
From: Jamie Bowden <jamie@photon.com>
To: "'William Herrin'" <bill@herrin.us>
Date: Tue, 28 Feb 2012 16:27:52 +0000
In-Reply-To: <CAP-guGV4hTVNfDuhA963GHNFW8L2FbmpmNqnAQJB7tXMZx1kuQ@mail.gmail.com>
Cc: NANOG <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
William Herrin [mailto:bill@herrin.us]
> On Mon, Feb 27, 2012 at 3:22 PM, Owen DeLong <owen@delong.com> wrote:
> > On Feb 27, 2012, at 12:02 PM, Brandt, Ralph wrote:
> >> Generalists are hard to come by these days.
> >
> > I think you're more likely to find a network engineer with (possibly
> limited)
> > programming skills.
>=20
> I wish. For the past three months I've been trying to find a network
> engineer with a deep TCP/IP protocol understanding, network security
> expertise, some Linux experience, minor programming skill with sockets
> and a TS/SCI clearance.
>=20
> The clearance is killing me. The two generalists didn't have a
> clearance and the cleared applicants are programmers or admins but
> never both.
Hey now...the time from zero to TS/SCI has gone from over half a decade to =
a mere quarter decade. You can totally pay these guys to sit around doing =
drudge work while their skills atrophy in the interim. Of course, if you n=
eed a poly on top, add some more time and stir continually while applying h=
eat.
Jamie
