Colleagues in my last company are measured by their token consumption. Not how little they use, but if they use up all their budget in a month. If not, they’re obviously bad for whatever they’re measuring.
I was a software tester ages ago and I was measured by the amount of bugs I found. Didn’t matter if it was a typo or some complicated crash that only occurred when all the stars aligned. I thought it was peak idiocy back then. But this new thinking beats that by far.
TehPers@beehaw.org 1 week ago
Yep, tokenmaxxing is a thing at some companies now. It often aligns with the same people competing to see who can generate the most lines of slop code (losc, which is different than sloc of course).
It wasn’t long ago where people understood that every line of code you write is a line of code that could have a bug in it. The good devs still know this, but many are also being forced to generate shitty code just to appease their shitty management now.
As an aside, I have yet to see a case where tokenmaxxing generates a profit for either the consumer or the provider. It just reeks of the same “market capture at all costs” mindset that have plagued SV startups for so long.
SeductiveTortoise@piefed.social 1 week ago
What has been maxxing for me is reviews. And if you send me one PR with 20,000 lines of code changed, I will tell you to get fucked and break it up.
I’m so glad my position allows me to do that 😂