| ▲ | simianwords 3 hours ago | |
Its almost become a meme at this point: well actually you can achieve the same using X so why waste tokens?! The reason you should use Claude and not playwright always is because the the invariant you wanna capture is at the natural language level. Like imagine I wanted to verify that Claude Code works and doesn't break. I can describe the invariant I want in natural language. Like: make sure that subagents don't block the original thread. Doing this in playwright means that you have already bought into some previously existing architecture which means your tests are now correlated to your code. Having the invariants written in natural language allows you to decouple code vs the invariant. I expect a lot of greybeard conservative programmers to keep opposing using AI here until eventually, not using AI will be seen as more risky. | ||
| ▲ | LelouBil 2 hours ago | parent | next [-] | |
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. | ||
| ▲ | fingerlocks 2 hours ago | parent | prev [-] | |
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. | ||