She called him an amateur for spending fewer Claude Code credits

On r/webdev a developer (u/eowenith) described sitting next to a non-dev friend trying to vibe-code an app with Claude Code. She bought credits three times in a single session. After four hours she had something that mostly worked. Then she pulled up the Claude Code summary screen, saw the developer’s historical numbers — a small fraction of hers — and called him “an amateur for how few credits and messages” he had used. We gonna be fine boys, the OP closed.

That moment is an inverted scorecard. To the non-dev, the credit dashboard reads top-down: more credits spent = more work done = more capable. To the experienced developer reading the same screen, the meaning inverts: fewer credits spent = better problem decomposition = more capable. The artifact is identical; its direction depends entirely on who’s holding it. Anthropic’s dashboard was never designed as a skill display — it records usage — but in the absence of any other visible signal of competence, it gets pressed into the role and starts carrying the metric. Whichever way you read it, the other side reads it the opposite way.

The same inverted scorecard shows up at organizational scale in the same thread. u/aghartakad described their company going full agentic, then two months later being asked to be mindful with token limits — “the development team was well under our limits but the manager was burning them fast”. u/CalligrapherCold364 named the underlying mechanism plainly: “efficiency isn’t visible to people who don’t know what efficiency looks like. Devs aren’t going anywhere, knowing why something works is still a different skill than prompting until it does.” And u/ShustOne pulled the consequence one step further: “a non-tech CEO will see the person who makes $50k as a viable option against the $110k developer. Good communication about what we do and why it saves time/money over the vibe coder is crucial right now.” Three different scales — peer, manager, executive — same broken metric.

For an indie maker working under stakeholders who don’t yet share the inverted reading, the response that does not” work is shipping better code faster. Better work is invisible to a stakeholder using the wrong metric — that’s the whole definition of the inverted scorecard. The response that does work is fixing the metric in a form the stakeholder can read: paper trail of token-cost-per-completed-task, before/after comparisons on identical problems, a weekly cost-of-rework column. Make efficiency “visible” on the same artifact the non-dev is reading. The OP’s friend won’t see it from the credit screen alone — but a side-by-side of “her four hours + three credit purchases vs his forty minutes + one purchase lands instantly. Inverted scorecards lose their power the moment both sides get scored on the same page. The work to do isn’t proving you’re better. It’s making the proof legible.