Not OP, but DevOps was supposed to be one pool of people taking care of everything, from infrastructure to networking to coding the whole thing. No handovers (or as few as possible), people who specialize, yes, but can take on a whole range of issues.
If Mark the networking guy is on vacation, Jane the fullstack dev should be able to perform basic networking troubleshooting and implement some fix until Mark returns and possibly fixes it.
Turns out people who can do that are:
- incredibly expensive
- very difficult to find
That's my take. I imagine a kanban board where prioritized issues are taken not by people who specialize in that particular area, but by whoever has the time right now. Again, I've actually never seen that implemented, except maybe for companies that consist of nobody but Jane and Mark :)).
In other places, it just means operations people with some basic coding chops. And they’re still a completely separate group, instead of an integrated team solving systems problems.
If Mark the networking guy is on vacation, Jane the fullstack dev should be able to perform basic networking troubleshooting and implement some fix until Mark returns and possibly fixes it.
Turns out people who can do that are:
- incredibly expensive
- very difficult to find
That's my take. I imagine a kanban board where prioritized issues are taken not by people who specialize in that particular area, but by whoever has the time right now. Again, I've actually never seen that implemented, except maybe for companies that consist of nobody but Jane and Mark :)).
reply