patternMinor
What is the utility of an inhouse DevOps if cloud providers already provide professional services?
Viewed 0 times
theinhousewhatprovidersprovideprofessionalutilitycloudalreadyservices
Problem
I've seen this in past roles when I was working a devops role as an employee.
What should be the purpose of an inhouse devops in a company that already pays for something like AWS Professional Services, in other words, the cloud provider has teams of engineers who are deployed on-prem to solve business needs, put together an infrastructure, and at the same time promote various AWS services to the client.
Where does the inhouse devops fit in this picture?
I remember some years ago I was in a remote meeting, solved a task, only to be told by my manager "okay, we'll give this to our consultant anyway". Not only was the remark awkward because the entire team was in the meeting, but I also don't see what the point of doing the task was in the first place if someone else would've been assigned to do it.
Does it make sense to take on a devops role if it's not for a cloud provider?
What should be the purpose of an inhouse devops in a company that already pays for something like AWS Professional Services, in other words, the cloud provider has teams of engineers who are deployed on-prem to solve business needs, put together an infrastructure, and at the same time promote various AWS services to the client.
Where does the inhouse devops fit in this picture?
I remember some years ago I was in a remote meeting, solved a task, only to be told by my manager "okay, we'll give this to our consultant anyway". Not only was the remark awkward because the entire team was in the meeting, but I also don't see what the point of doing the task was in the first place if someone else would've been assigned to do it.
Does it make sense to take on a devops role if it's not for a cloud provider?
Solution
Some good reasons could be:
BTW, IMO the best consultants are those who:
- The salary of an inhouse devops is pretty sure less expensive as the consultants.
- The consultants are only assigned during a limited period, to temporary add (wo)manpower, e.g. while putting together the infrastructure.
- The consultants come with specific expertise that the inhouse devops do not (yet) have, whereas part of the job of the consultants is to perform knowledge transfer and/or on the job training for the inhouse devops.
- The consultants are there to do the boring parts of the work, whereas the inhouse devops are assigned to the strategic / long term tasks (so that when the consultants leave, the know how doesn’t leave the company also.
BTW, IMO the best consultants are those who:
- Say their jobdescription is like “My job is to make sure that you don’t need me anymore ...”.
- Never touch the keyboard, and instead always coach / help inhouse devops to have them complete any task (it seems so easy when you see somebody else complete some task, but it is way more difficult to complete it yourself).
Context
StackExchange DevOps Q#14009, answer score: 2
Revisions (0)
No revisions yet.