This article feels like the result of having unlimited tokens at your disposal. It’s got some very expensive practices, where near-free practices would produce the same or better results.
There’s a long section in the middle where the article describes per-change verification via skill files and “ask Claude to use the chrome-for-Claude tool” when checking if changes have introduced regressions.
But there’s already tools which do this without spending tokens tokens. Playwright will achieve equal quality but deterministic results across the same verification attempts. It is write-once-use-often, so has a marginal cost near zero.
A key pillar was introducing things like static analysis to provide cheap deterministic checks as the first goal and only then moving to other forms of verification.
What makes you think they are not using Playwright ?
For me this article is more aimed at devs that are still stuck treating code generation and verification as two separate tasks. Giving agents the right tools (including playwright) to do both at once makes things more token efficient, not less.
Its almost become a meme at this point: well actually you can achieve the same using X so why west 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.
Wait, are you saying a company that makes money from selling tokens generated a content piece recommending people solve their problems by using a lot of tokens?
> Nobody can read every change, so we use failures as one way to decide what needs a person.
Whether a human can or should review every diff is a conscious project level decision. I have yet to see a project where it is not feasible. The trick is to break things into small enough pieces that you can review them. Just like one would do if you were doing such changes manually. Nobody in their right mind performs non-mechanical changes of 100s of files.
The more I read articles like this, the more I realize Claude is good for process prototyping, but you need to "bake" the process with flat code/script/organization to decrease costs.
The future of IA would actually be to large scale prototype easily, even more like Python was a prototype language.
You should fire yourself and have your boss go all in on anthropic duh. If you are the boss then you either shouldn't have gone down this path, accept your code won't be verified, or shut your doors.
Exactly this. I build large systems like erp, ipaas just from a Claude team with two premium licences. everything builds, verifies, deploys itself. I can track everything and implement features in a days. security and big fixing is background work. I would love to know what 2000$ worth of tokens do in your business.
Verification is the bottleneck and that's why we're building https://Proofline.sh
Starting with infra evidence and soon expanding to application verification loops. This is a very exciting place to build and we're seeing great results once the verification loop is closed for the teams
Issues are automatically closed after being inactive for too long. It's also true that many issues that are filed there have nothing to do with Claude Code proper. To conclude, these numbers (either many open, or many closed, or any relationship between them) a-priori mean nothing either way.
They poached a lot of people from companies like Google that have solid engineering practices. I imagine it's a culture issue if anything, not a knowledge/background issue.
Apparently, the remaining 10% too, but not attributed correctly, so they are careful of claiming it as Claude-written. (Can't remember where I've read that.)
There’s a long section in the middle where the article describes per-change verification via skill files and “ask Claude to use the chrome-for-Claude tool” when checking if changes have introduced regressions.
But there’s already tools which do this without spending tokens tokens. Playwright will achieve equal quality but deterministic results across the same verification attempts. It is write-once-use-often, so has a marginal cost near zero.
A key pillar was introducing things like static analysis to provide cheap deterministic checks as the first goal and only then moving to other forms of verification.
For me this article is more aimed at devs that are still stuck treating code generation and verification as two separate tasks. Giving agents the right tools (including playwright) to do both at once makes things more token efficient, not less.
I think future AI cost will be as cheap as doing an API call in classic sense.
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.
Do you not see the propaganda through the pseudo helpfulness?
Scandalous.
Not that it is an explicit, conscious direction, but it very much is one.
You’re not wrong, in that free flowing tokens are enough to convince such a group it’s simply good advice.
Whether a human can or should review every diff is a conscious project level decision. I have yet to see a project where it is not feasible. The trick is to break things into small enough pieces that you can review them. Just like one would do if you were doing such changes manually. Nobody in their right mind performs non-mechanical changes of 100s of files.
The future of IA would actually be to large scale prototype easily, even more like Python was a prototype language.
Im already spending my $2k usd per month in tokens with just one or two agents. How do they expect me to do that?
Starting with infra evidence and soon expanding to application verification loops. This is a very exciting place to build and we're seeing great results once the verification loop is closed for the teams
this u?
"The resource at “https://claude.dev/_next/static/chunks/241gnzjfqbp9f.css” preloaded with link preload was not used within a few seconds. Make sure all attributes of the preload tag are set correctly."
I am more interested in the remaining 10%.
“Also Claude, but we're fixing up the attribution to be super confident before claiming it”
https://x.com/bcherny/status/2111207278653399460?a=CQxYPj8Va...