Paul Kedrosky sees a bubble. Azeem Azhar sees a productive boom getting "a little bit stinky." The new calculation for Operators to run is the the cost of a finished task.
Good point : “The buyer’s equation has a denominator: tokens times price, divided by the work that actually got done.” And I would add "done and meeting expectations/objectives" because often, it is not the case AND my addition also implies a quality check (human) that also has a cost. The increase in use of agents makes it faster to "produce" but the new bottleneck is verification. Verification is especially tricky because you may not know what was used to produce the output and you have to spend quite a bit of time and energy in investigations. Then, if you flip it, the curation effort (the inputs) should also be factored in.
Looking at it from the buyer's side makes far more sense to me, since whoever signs off the invoice cares about what got finished, whatever the compute bill says. That point about rationing is the part I'd love to see you develop further. Do you think it shows up first in procurement budgets or in teams going back to doing certain jobs by hand?
Once usage has a budget code, whoever owns that code is accountable for how much finished work the spend bought, not just for the size of the bill. Incredible work as usual, John!
As always great perspectives to question the value and the price tag it deserves. Thanks John! 🙌🏼
Thanks so much, Nihal!
Good point : “The buyer’s equation has a denominator: tokens times price, divided by the work that actually got done.” And I would add "done and meeting expectations/objectives" because often, it is not the case AND my addition also implies a quality check (human) that also has a cost. The increase in use of agents makes it faster to "produce" but the new bottleneck is verification. Verification is especially tricky because you may not know what was used to produce the output and you have to spend quite a bit of time and energy in investigations. Then, if you flip it, the curation effort (the inputs) should also be factored in.
Appreciate you, Bertrand. 🤓🙏🏻
Important heuristic I don’t hear anyone else talking about: Cost per finished task. Great stuff, John.
Looking at it from the buyer's side makes far more sense to me, since whoever signs off the invoice cares about what got finished, whatever the compute bill says. That point about rationing is the part I'd love to see you develop further. Do you think it shows up first in procurement budgets or in teams going back to doing certain jobs by hand?
Once usage has a budget code, whoever owns that code is accountable for how much finished work the spend bought, not just for the size of the bill. Incredible work as usual, John!