I have Claude Code Max $200 a month plan. I ran aggressively for 4 days and ran through 80% of Opus 4.6 for the week. I was also running it 16 hours a day. Today and tomorrow I will wait until 5pm PST because they have a 50% special to run with the remaining tokens.
The problem was testing it against 5 websites at a time after every change to instructions to ensure there wasn't any regressions. The orchestrator agent tracks all token expenditure and would update its own instructions to optimize.
Another interesting fact about plot sizes in Europe: You can see within an area which kind of inheritance law was in place: If farming plots are large, usually the oldest son inherited everything. If they are small, they were evenly distributed.
I am utterly confused at how you think rewriting entire libraries have less security holes than battle-hardened libraries that 1000s of other people use.
- Generating your own left pad means you don't have to pull in an external left pad
- Which in turn means left pad doesn't show up on your SBOM
- Which in turn means CVEs won't show up for left pad when you run your SBOM through through SCA
- Which means you don't have to do any CVE triage, risk analysis, and mitigation (patching) for left pad
- It also means you don't have to do SOUP testing for left pad
Now imagine you've done that for a dozen libraries that you are only using a small piece of. That's a ton of regulatory and cybersecurity work you've saved yourself. I never claimed generating code makes your software more secure, I claimed it can reduce the regulatory and cybersecurity burden on your SDLC, which it does as demonstrated above. Taken to the extreme (0 external dependencies), your regulatory burden for SOUP and SCA goes to zero.
Defending that particular kind of driver: He might not have known to be the last car. But one thing he knows for sure: a long line of cars in front of him. Speeding up or keeping distance is pointless, so he uses that moment to be friendly instead.
reply