Others here hates how DevOps pushed parts of operations workload on Devs? Just this afternoon I have to fix a CI issue and then find a way to connect a microservice I built to production MongoDB; I'd be okay with that (I love to thinker with servers) if not for the fact which I have to do it trough leaky and badly documented abstractions put up by the customer. I was having a nice productivity streak but when I have to do this kind of shit the motivation quickly plummets.

In tiny to small businesses, DevOps always was something the dev has to do too. But i too don't see, why suddenly everyone would need to be an admin in bigger companies too. If you can afford to have a DevOps specialist and there actually is DevOps to do - then you should have a specialist for that.

After choosing the wrong language for the job, having someone with a negative DevOps skill do DevOps is hurting security the most. that is how all the unsecured mongo instances happened...

It's a matter of size and workload.

If it's a small company, devs will be expected to handle ops too.

As companies grow, and the ops workload increases, it's natural to get a DevOps specialist to handle it, and leave the devs to, well, develop.

To me, a great DevOps had to be first and foremost a dev.

I've had the misfortune to work with DevOps that were so clueless that wouldn't even know how to set up the runtimes required for a project.

No shit, they would actually ask *me* to give them the exact commands to get node, php or python running...

And I was like... "Dude, it's your infra, you don't even let me into it..."

Depends.

DevOps is *heavily* unspecific like most job descriptions in IT.

"Connecting a microservice to production MongoDb"..."tons of abstractions"... Somehow this makes my red flags popping up like pimples in severe acne.

Usually you should have connection details, a configuration and documentation, git commit be done.

If you need to find out how the database is configured and there is no simple configuration possibility, then this is to me an software architect problem. Someone fucked up badly. You should never need to read software source code to find out how to add a configuration, Data Source Names etc. exist for a reason.

For me this has nothing to do with operations at all - unless the MongoDb production server needs to be configured as in ACLs or stuff like that.

Would be interested to know what has happened there, cause that really sounds like architecture mayhem.

Despite the company size, more and more positions mention DevOps skills and/or responsibilities in their software development openings, it's quiet nasty and I reject this mix if not provided with a 2x income. End of the story.