"Since the car wash is only 50 meters away (about half a football field), you should walk.
...
When driving might make sense instead:
You need to move the car into the wash bay.
..."
So close.
Interestingly, Sonnet 4.6 basically gave up after 10 attempts (whatever that means).
```
Claude Code v2.0.13
Sonnet 4.5 (with 1M token context) Claude Max
/Users/jesse/tmp/new-tool/.worktrees/todo-cli
```
How does this person have access to Sonnet 4.5 with 1m token context? I don't see this referenced anywhere when I search or when I ask Claude about it.
It’s a limited release beta feature not available to all. You can try to activate it by doing:
/model sonnet[1m]
And it accepts it but the at the next API call it may fail and say “this beta model is not available with your subscription”.
I haven’t gotten access yet.
One of the nice things about Codex (GPT-5) is the supposed 400k token context (although performance starts to deteriorate when you get to 80% context usage).
From a related nature article (https://www.nature.com/articles/d41586-024-02383-9), "null or negative results — those that fail to find a relationship between variables or groups, or that go against the preconceived hypothesis." According to this definition, I think both examples you provided are null results. Particularly here, where the context is the file drawer problem.
Thank you! Those are good points. I'm still trying to figure out what the differentiating factor is for other people. For me it's the ease with which I can replace a QR and receiving a notification even when I'm not home
I created this nozzle pattern package as an alternative to the circuit breaker pattern. Would appreciate hearing any ideas on how to improve it and if there are already circuit breaker alternatives out there!
In this case, complaining made me aware of the issue. I've known about patent trolling but not this particular kind. So complaining is a form of raising awareness which could be a good first step if system reform is needed.
I'm sorry for all the negative comments you're receiving in this post. I'm sure you worked really hard on this and I know it sucks when you share something like this and all people say is negative things.
My team and I have actually been looking for something like this. Not to judge engineers productivity but to understand workload imbalances. For example, say we notice 2-3 people are doing all the PR reviews (something I think we could detect with this). Maybe the other engineers need training on PRs or we need to set expectations that everyone reviews PRs or maybe our PR load balancer isn't set up correctly.
So, good work and good luck. I'll definitely be showing this to my team. Thanks for sharing this with everyone!
Thanks a ton! If you have any feedback/needs that the app doesn't currently account for, please email me of send the feedback from directly within the app!
reply