In my opinion, any infrastructure that's not going to be thrown away very quickly (and even then I'd argue that codifying it is still probably better) should be expressed as code. I once worked somewhere where everything was provisioned by someone clicking through the AWS control panel and it was an enormous mess. The repeatability of infrastructure expressed as code is invaluable, not to mention the documentation aspect of it.
You mentioned at the start things like, "DevOps position" or "DevOps job", and I'd have to assume you left your current organisation to do that. DevOps is a culture not a job title or a team within a company. Either everyone is doing DevOps or no one is. I guess that's something to take up with WyeWorks... :)
Developers should have full operational responsibility for the code they write, and that has to include the infrastructure it runs on. Infrastructure as code is a great tool for achieving that.
In my opinion, any infrastructure that's not going to be thrown away very quickly (and even then I'd argue that codifying it is still probably better) should be expressed as code. I once worked somewhere where everything was provisioned by someone clicking through the AWS control panel and it was an enormous mess. The repeatability of infrastructure expressed as code is invaluable, not to mention the documentation aspect of it.
You mentioned at the start things like, "DevOps position" or "DevOps job", and I'd have to assume you left your current organisation to do that. DevOps is a culture not a job title or a team within a company. Either everyone is doing DevOps or no one is. I guess that's something to take up with WyeWorks... :)
Developers should have full operational responsibility for the code they write, and that has to include the infrastructure it runs on. Infrastructure as code is a great tool for achieving that.
I've been there too, AWS is too complex to be clicking on it! Regarding DevOps I agree on what you said ☺