logoalt Hacker News

techblueberrytoday at 2:53 AM2 repliesview on HN

So touche, but since it's usage per task it's kind of weird.

This means that the average engineer is efficient at (say) identifying the first 10 tasks they should do but there are diminishing returns after that? That seems like a weird pattern. Wouldn't it be more likely that certain tasks have a ROI based on how efficient the task is generated?

Like I'm trying to imagine in my head, if you think an engineer is more efficient with the tool, why deny them more tokens. I guess so they think to use them more efficiently?

So, maybe I conclude that I think your conclusion that there must be $1500 per engineer is flawed. And even if it were true, I don't think the benefit would be evenly distributed. I suspect this is a first pass at figuring how to budget them and there will be a second pass.

While it certainly reeks of motivated reasoning, Jensen Huang assertion that an expensive engineer should be using at least their salary in tokens feels more logically sound to me (assuming the average engineer is efficient at using tokens, I have a feeling it's a normal distribution)


Replies

therealdrag0today at 5:38 AM

Setting a cap motivates developers to invest their tokens wisely such as choosing the right models and not burning tokens for fun or side projects, same as any budget.. it’s not any deeper than that.

At my company we can ask for temporary cap limits if it’s justified, which is fairly common.

simonwtoday at 3:08 AM

"I suspect this is a first pass at figuring how to budget them and there will be a second pass."

Completely agree with that.