4 ms·
So, I had this argument/conversation with Jedberg (who incidentally also works at Netflix); I said that: DevOps means different things to different people; To
by dijit 5y ago
So, I had this argument/conversation with Jedberg (who incidentally also works at Netflix);
I said that: DevOps means different things to different people;
To Some: it's the evolution of "Operations" to integrate them into the team so that operational issues are automated out and that developers can get greater velocity.
To Others: it's a sysadmin who can use CI/CD and fumble through scripting something.
To the majority: it's a developer who can fumble through installing a server or package, and this is jedbergs definition too, and one he argues is canonical.
My opinion is that specialising is important.
---
To this effect: it's _far_ too much cognitive load to understand how your OS works, your application, its framework, the cloud provider, the logging tools, SLI/SLOs and error budgets, on-call policies and alerting mechanisms, application level security, authentication of systems, authorization of systems, SSO, etc;etc;etc;etc;
Because to learn all of those various things and weigh them in your head every time you make a decision is fatiguing, it took me 10 years to get "great" at Ops and a decent scripter; it's possible that Ops is easier than programming but from what I understand it's not easier, it's just different.
With Development (exception: Javascript) you learn primitives and they rarely change. With Ops, the tools and landscape change _frequently_.
10 years ago it was Nagios, then Zabbix, then some combination of graphite and co, now it's prometheus, maybe Thanos or is it influxDB+Kapacitor?
That's just alerting, there's new and changing solutions for logging, message queues, databases, IdP tooling (keycloak, vs FreeIPA vs AD), distributed tracing systems, heck even load balancers (GCE Ingress vs Nginx vs traefik vs etc;etc;etc).
Hell, understanding how Kubernetes works is basically a full time job otherwise "black magic is happening" and debugging becomes a nightmare.
Frameworks change or get replaced too, but it doesn't feel like it's close to the same rate as infrastructure software.
I remember at college one of the professors said to me: "It's impossible to know everything about computers, because as you're learning: new things come out, and after you've learned something: it will change. The more you learn, the more you have to keep up to date until you can no longer keep up."
I think maybe people don't think like that.
I think we need to have people of different disciplines.