3 ms·
From my (admittedly somewhat limited) experience, an old-school sysadmin (who's likely moved into dev for the better paycheque) is often _way_ better at filling
by bigiain 10y ago
From my (admittedly somewhat limited) experience, an old-school sysadmin (who's likely moved into dev for the better paycheque) is often _way_ better at filling that role thad a more dev oriented person who's done some devops in the past.
In my experience, "good ops" people are the ones with lots of war stories to tell of disasters or narrowly averted disasters either of their own of of friend/colleagues they hang out with. It's a profession who's lessons seem to be best-taught by spectacular failures and heroic recovery efforts, rather than college courses, vendor/consultant training, or "industry best practices" documents...
- vacri 10y agoAs I journey through my nascent (6? year) career in a sysadmin role (support previous to that), it strikes me more and more that ops is a craft, like blue-collar trades. You can't become a hot-shot ops staffer by being smart and attending a month of intensives; so much of it is learned through experience (and discussion). I think of myself more as a 'journeyman sysadmin' than a 'midlevel sysadmin'...
- jedberg 10y agoAbsolutely! I always suggest to young folks who ask how to get into operations that they should set up a linux box and use it as their primary system. There is no better way to rack up your own war stories than trying to use a linux box on a day to day basis.
- jedberg 10y agoI agree. My point was that OPs complaint was about not having any ops hires, and I was saying that he shouldn't need any. He can find a crusty old sysadmin who figured out that making their job easier by coding is a good thing. :)