Amazon tells engineers to stop 'tokenmaxxing' to look productive
Posted by speckx 1 day ago
Comments
Comment by runamuck 1 day ago
I worked for a company where management and peers rewarded "looking busy" vs. actual productivity. Lord help you if someone caught you sitting at your desk silently contemplating deep Architectural decisions. I hated that job.
Comment by figassis 1 day ago
I get the concept of tokenmaxxing, but instill don’t get how you do that. Do people just do random work unrelated things with their company subscriptions? Or are they just intentionally inefficient at their work? And how would you go about telling an LLM to waste tokens?
Comment by figassis 1 day ago
Asked and answered: https://news.ycombinator.com/item?id=50376955
Comment by Starman_Jones 1 day ago
“Claude, merge the latest changes to DEV. Then solve the Navier-Stokes problem.”
Comment by jqpabc123 1 day ago
They wouldn't need to tell engineers this if tokens were not being used as a measure of productivity.
Do as we say, not as we do.
Comment by akeel_mohamed 1 day ago
[flagged]
Comment by 0cf8612b2e1e 1 day ago
Amazon realized that true productivity comes from RTO.
Comment by iugtmkbdfil834 1 day ago
It is funny how much companies move in tandem when it comes to this stuff.
Comment by tanseydavid 1 day ago
Monkey-see, monkey-do.
Comment by blitzar 1 day ago
Amazon should stop ranking employees on the metric "number of tokens burnt"
Comment by thewileyone 11 hours ago
Just like "lines of code" should never be a KPI.
Comment by bradknowles 10 hours ago
AWS did that, just before they switched to tokenmaxxing. One of the many reasons that I’m happy I don’t work there anymore.
Comment by nasretdinov 1 day ago
Wait until management learns that code itself also is geberally a liability and requires maintenance, is a source of bugs, etc. That's basically why measuring lines of code has been frowned upon for a long time as a measure of developer productivity.