Hacker News Reader

Full thread

pfoof

Me, a DevOps Engineer, company less than 40 people:

- physical servers and VMs

- some microservices

- CI/CD pipelines for every project

- helper scripts

- licenses

- security

- e-mail accounts

- setting up everyone's computers

- wiki and documentation

Moreover:

- understanding compilers and frameworks because "we developers want only to code"

- printer, routers, switches, TV

This is not a rant, just proof for this article.

View on HN

This is extremely similar to my DevOps role. Company about 250 ppl, 4 DevOps engineers.

As a ex-product lead (full stack dev) and head of engineering, the “we developers want only to code” winds me up so much.

Just because your code worked once and now another dev has (badly) applied a framework upgrade, doesn’t mean it’s DevOps’ job to find out “why the build is broken” and fix the incompatibility between your old code and the new framework.

This just seems like Ops?

Yes, more ITOps and TechOps but I'm trying to make everything into IaaC from the current state of things

Reply on news.ycombinator.com