Before you hand off implementation to a model, make the build-vs-buy call yourself. Models optimize for what compiles today and solves the problem faster, not for the maintenance risk. Sometimes that's the right call. Sometimes it isn't.
What are your thoughts?
And in the end the guy who asked for the feature will look to the finished app, realize the original request was simply missed in the process, and get back to his old Excel spreadsheet.
For me, a solution was to build a quick local tool to track my daily token budget and keep tabs on spending, so I actually know if I'll make it to month-end.
How are you solving this problem today?
Managing token costs is becoming increasingly unpredictable these days.
Depending on the model, tools, and API changes Anthropic makes, costs and outputs vary in random ways. You never know if you will have enough dollars.