upvote
The better thing is do use both, use claude to convert the invariant to deterministic code, and review said code to be sure it matches your natural language idea of it.

The issue with only having the natural language specification is that it is non-deterministic.

reply
That’s a terrible example because you can verify that at runtime by attaching thread watchdog daemons. This is invariant across all languages natural or otherwise, invariant to the binary, invariant to tokens or context, invariant to network access, and you can set the assertion, making it invariant to the thing your trying to accomplish.

I expect a lot of no-beard man-child programmer wannabes will brain rot early in their careers and find themselves wallowing in the hopeless despair of sitting in front of a computer arguing with a chatbot for decades on end, living a life trapped under the weight of endless mediocrity, unknowingly desperate for a modicum intellectual stimulation that you’ll never find because you can’t prompt for that, bro.

reply
If you re architecture threads to processes, you have to rewrite your tests.

That was kind of my point. Natural language almost always survives rearchitectures because your higher level interface to your end customer rarely has churn.

In a few years, agent driven testing will become normal and almost expected in some enterprise companies. Obviously we will still have people like you opposing it on grounds of “but just write tests in playwright”.

I also find the greybeard archetype fascinating. They’ve opposed almost everything new including Cloud, microservices, kubernetes. Now with AI. And here in this thread with AI driven tests. They seem to think programming should be done exactly how it was done when they were in the prime of their career. Anything before that is archaic and anything after is hype.

reply