I have a script at work that writes out some config files and I'm having Claude run them after making changes. The script if it detects breaking changes will spit out a message saying what the breaking changes are, and not do anything, telling you to rerun it after validation with the override flag.

If I don't tell Claude about this behavior, it ignores the script output and lies about passing tests that validate if the config files were regenerated.

So I added to my prompt instructions to observe it, and if it sees that message, double check its work and then inform me and ask what to do before proceeding.

This has had the net result of Claude either running the script with the override flag from the get go (explicitly forbidden) or it seeing the message and convincing itself that the override is warranted and running it a second time with the override flag. It's never once stopped to ask me what to do like instructed.

This is one of a few reason I strongly prefer GPT and its codex variants. It seldom frustrates me, sure its not omnipotent in any way, but it just feels very "tuned in" when it comes to understanding intent and scope.

Imagine worker that did loop of "you're absolutely right -> same fuckup again" multiple days every week, wasting time of whoever told them to do the task

They'd be out of company after a week

It's just the worst version of capitalist game theory. If I don't do the bad thing and get rich, then someone else will do the bad thing and I won't get rich.

Why not? Blacksmithing and coding have a hell of a lot in common. In both disciplines toolmaking is extremely important. Often you have to make custom tools to accomplish a design--e.g. a twisting wrench or a form tool. Sometimes you have to make tools that get used once and thrown away, like a jig temporarily welded to a piece to hold it in place while you build its sibling assembly. Sound familiar? I do this kind of thing all the time in code.

Another similarity is the relative simplicity of the underlying structure of the system. You essentially have two hammers (one small one you swing with your hand and another big one that is planted on the ground), some material, and some heat. You build the rest.

Another similarity is the resistance to automation. A skilled blacksmith is a versatile worker. You can create assembly lines to automate any one thing they might produce. The end product will not have the same quality--it will not truly be wrought iron, each piece will not be unique, there will be nothing of the aesthetic taste of the artist in it, but if you're just some bean counter who doesn't care about those things you'll be able to sell it. But if you need the optionality to produce any of those things.. automation is not your friend. And some things just cannot be automated, at least not without extreme costs or very poor results--shoeing horses comes to mind.