Claude Code for devops / iac right now as IC. LLM writes most code, I manage guard rails, style, success criteria etc. To be fair, writing code was never really the biggest part of the job, it was always figuring out what people need, what solutions make sense for what team in what context, talking to people, documenting things, testing etc. CC can be helpful for this stuff also, particularly exploring options and doc gen.
The tool works more or less perfectly for my relatively simple use cases. IAC codebases tend to be smaller so context management easy. It could be more capable of course but from my perspective there are no major cons. Typically I have 3 or 4 repos checked out into workspace and the tool is managing how to "stitch them together" / integrate. Having a local workflow is pretty key, one missing piece for me right now is being able to easily iterate on work that can only be tested by running a pipeline (without manually shuttling data between tools).
I don't think I actually deliver any faster because in enterprise you spend most time in wait states blocked by slow internal processes (ticket for X, approval for Y, meeting to discuss Z, 20 minute deploy pipelines). It would require major org transformation to shift this, seems unlikely to happen in the next few years.
I will say, my job feels easier and my cognitive load lighter. I don't need to "switch modes" as often between high and low level thinking. It "feels" like having a fairly capable junior (who nonetheless needs careful management and supervision) to handle the details.
