2 ms·
I think the important aspects are making individual developers responsible for their costs and restricting the most expensive models when costs are too high. Th
by arendtio 2mo ago
I think the important aspects are making individual developers responsible for their costs and restricting the most expensive models when costs are too high. That way, people have a chance to learn when they tend to use the most expensive models for trivial tasks.
- jgilias 2mo agoDefinitely. I can easily cut my individual AI spend by 50% at least. But I won’t, until someone tells me to. For three reasons: 1. Thinking about how to optimize AI spend is one more thing to think about when I have too many things to think about already; 2. If there’s even a minuscule chance that me selecting down the model results in a task getting delayed because for that particular thing the model happened to be “too dumb”, I’m just not going to do that. Because I’m evaluated for what I ship and saying, “oh, not happening this week because I downgraded to Haiku for the exploration phase, and that resulted in a faulty plan, so it slipped a day” just doesn’t cut it. 3. Why should I spend time thinking about costs, and risk being slower because of that, if the next guy doesn’t?
- emanuelecella 2mo agoYou shouldn't have to. The gate should be automatic and not a decision you make per request but a hard cap enforced at the infrastructure layer before the call happens from your providers