> Editing Go templates that generate YAML is absolutely miserable, it is my least favorite task. Claude gets it right without fuss every time.

As I understood it, the article's thesis is that your system shouldn't require "Go templates that generate YAML" in the first place.

Which is the sort of thing I'm very sympathetic to, but seems overstated here. There's a balance to strike.

Yeah. I would personally refuse to add Helm to a system but the complicating factors are 1) customers ask for it by name (why I relented at my last job where we made self-hosted k8s software) 2) people we hire know how to use it. So while I find it unpleasant from a computer science purity standpoint, it is pretty popular and gets the job done. I have to save my energy for things that matter and improve the experiences of the customers, not design the 900th way to deploy stuff to Kubernetes. So ... I am happy to let Claude double-check my {{ brace }} nesting or whatever. If something is Objectively Terrible but tooling smooths over it, I can let it live without a fight.