Story

Sysadmins take 'WAY too much crap from developers.

Almost every dot-com I have worked at or the past twenty-plus years listened 'WAY too much to developers, and allowed things to be rolled out, that shouldn't have been.

Almost every dot-com I've worked in the past ten years was started up by developers who called me in when things got too complicated for them to administer, and develop code, at the same time.

Almost every dot-com I have communicated with in the past two or three years seems hell-bent upon moving everything into 'The Cloud'. WHICH cloud? That changes about once every eighteen months, it seems.

Recruiters are now looking for these new-fangled 'devops' - these would be software developers, who do hardware operations - or is it hardware operators, who do software development? - to do twice the work, at half the price.

By my count, the average number of programming languages, technologies, vendor product lines, networking protocols, etc that one is now expected to master exceeds that of the average UN polyglot translator by a factor of ten.

It's pretty clear the people making up these job descriptions are only counting the money they will save by hiring one person to do two jobs and have NO CLUE what goes into either software development OR hardware operations.

We sysadmins need to start pushing back more!

And so it's great to see collective some movement against systemd.

Even if I am a BSD guy, at home, I still wrestle with Linux, at work - and so I share all of your concerns.