alt Hacker NewsI honestly can't imagine using a bigger plan. The $20 a month plan is able to be used almost all day without hitting the usage quota so long as you moderate what model you're using.
I really don't understand why so many people seemingly use the bigger plans. Are people just running opus 5.5 as 4+ subagents 24/7?
In order for me to actually understand what's being done, I always keep it brief and use specific prompts (and usually use smaller models since they're perfect for that). Do people just let "claude take the wheel"?
When you have to go in to your next standup and explain what your code does to your boss, and what you've done since the last meeting, what do you say?
Replies
> When you have to go in to your next standup and explain what your code does to your boss, and what you've done since the last meeting, what do you say?
I hand them a writeup of how incorporating agentic decision making into cleaning up some of our messy data saved us $XXX,XXX at a cost of $XX of tokens, with the receipts attached.
I run 4 agents under one supervisor agent for 12 hours a day building computer use environments. Yes, I don't read the code, but testing is 90% of my work. Got to find other ways to buy trust in AI code. I came up with a stack of 5 layers of testing which is pretty similar to the recent Anthropic writeup. I can consume the $100/mo plan weekly quota in 2 days.
How do you get along with the 20USD plan and that much utilization?
I use Claude mainly via Webinterface and when on Opus 4.8 or higher, I reach my weakly limit around 2 - 3 days before rest - and Im just prompting single/specific very limited & constrained classes & functions with proper description and architecture upfront.
> Do people just let "claude take the wheel"?
Yes, I'd wager most people just let "claude take the wheel".
> When you have to go in to your next standup and explain what your code does to your boss, and what you've done since the last meeting, what do you say?
You say "Claude, I've got a standup in 10 min, give me a high level summary for my boss of everything you did since the last standup" and then you read that lol.
I let Claude take the wheel with various non-professional projects which often means heavy subagent workflows. Prompts like this easily eat through my 5x Max plan limits:
> I want you to look for UI issues related to transitions. Look for jumps, reverts, or anything that doesn't follow UI/UX best practices. You might need to figure out how best to even record and review UI transitions. Do all testing locally on a local dev server, but make sure to undo any database changes you make in the process of testing. Be exhaustive and report back with an .html report that highlights the visual issues and proposed solutions so I can review each one. Ultracode on.
Which means I have up to 10 Opus 5.5 medium agents running concurrently for long stretches of time.
I want to be clear I don't think that using Claude in this way gets you the best possible results. But when the app is fully vibecoded then audit prompts like the one above can be seen as a definite net positive. Making Claude think really hard about various improvement routines will get you better results in that one aspect than Claude's first attempt to build something from scratch did.
> When you have to go in to your next standup and explain what your code does to your boss, and what you've done since the last meeting, what do you say?
You say the same thing to your boss as if you were a lead or manager reporting on a project that your junior and mid-level devs are working on. "What" is the easy part to explain; "how" is the details that your manager doesn't need to hear about if you're doing your job properly.