People don't pay double the $100 account in fixed recurrent payments if they don't intend to use a lot more than they would use in the $100 subscription.
Perhaps people at Anthropic should ask Sonnet (or Kimi, it's much better value) how power laws and pareto distributions work? You are advertising for people who can justify a virtually unlimited amount of tokens, why is it surprising that they would use as many as you're offering them in the plan?
PS: interesting that you'd use a throwaway account to post this
If you manage developers or product folk, do you allow them to work when you're not looking over their shoulder? All developers can be managers/team leads now. You plan, you delegate, you review.
You're welcome to not do this, surely that's appropriate in quite a few areas of work, but many of us are because we can get more work done than if we we're micromanaging every line of code change. For startups, where a bit of quality can suffer in favor of finding market fit, this is huge.
Every morning it summarizes a bunch of stuff for me, suggests me PRs to review, emails to reply to, freshly cloned any new repos, pulled all others, presents me with the suggested approaches to my PRs of that day, and gives me a list of my slack mentions that look more urgent.
This is just the morning ones, and saves shitloads of time of clicking around from tool to tool, freeing up time for the thinking and deciding.
I think maybe you still don’t understand that not everyone will max out their usage, regardless of the methods available.
People don't pay double the $100 account in fixed recurrent payments if they don't intend to use a lot more than they would use in the $100 subscription.
Perhaps people at Anthropic should ask Sonnet (or Kimi, it's much better value) how power laws and pareto distributions work? You are advertising for people who can justify a virtually unlimited amount of tokens, why is it surprising that they would use as many as you're offering them in the plan?
PS: interesting that you'd use a throwaway account to post this
I need a hypothetical use case for things like this, I don't get how so many people have so much desire for use of features like this.
https://martinfowler.com/articles/harness-engineering.html it's being talked about everywhere.
If you manage developers or product folk, do you allow them to work when you're not looking over their shoulder? All developers can be managers/team leads now. You plan, you delegate, you review.
You're welcome to not do this, surely that's appropriate in quite a few areas of work, but many of us are because we can get more work done than if we we're micromanaging every line of code change. For startups, where a bit of quality can suffer in favor of finding market fit, this is huge.
The actual /loop and cron are beyond the normal "agentic loop"
1 reply →
Every morning it summarizes a bunch of stuff for me, suggests me PRs to review, emails to reply to, freshly cloned any new repos, pulled all others, presents me with the suggested approaches to my PRs of that day, and gives me a list of my slack mentions that look more urgent.
This is just the morning ones, and saves shitloads of time of clicking around from tool to tool, freeing up time for the thinking and deciding.
Wow, you should probably ask it to write a script for 90+% of that instead . Sounds like a huge waste of electricity.
1 reply →
Deduplicating/validating/processing incoming bug reports?