this post was submitted on 03 Jun 2026
440 points (98.9% liked)
Technology
85342 readers
4261 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Whole concept of "how much AI you used", is so flipping stupid of a metric I can't even wrap my head around. I mean even if we assume it's their own AI they are using... that's their power etc... That's like a leaderboard for most gas used up, or miles driven by your truck drivers.
It's the old lines of code metric style of thinking.
The people in charge only know line go up means better and bigger number is better.
Its only when things go wrong and someone ELI5 for them that they listen. And even then it'll wear off in a week and they'll be on to their next make the number bigger obsession.
I've had to explain this to more executives than I wish to remember. Computer code is a recipe, not a cake. When you see a recipe that's super long, and requires two kitchens worth of bakeware and tools, you probably think it's a bad recipe. Short, elegant, easy to follow recipes with a little note in the margin from your grandmother about what to do when the dough is too sticky are the best recipes.
Unfortunately, one learned the exact wrong lesson from this, and started measuring lower lines of code produced as better... Which worked for a while, but lead to a lot of weirdness around new features for no particular reason.
I love this metaphor. totes stealing it. 😊
"Sorry, can't add that feature. That would take at least another 20 lines of code and I can't lose my leaderboard ranking. Not with Steven in second place..."
I've said it for years: qualitative is better than quantitative. It's just that it doesn't look as nice and objective on reports. This obsession with numbers has been a bane on society for a long time.
Hey boss, I just got that new feature submitted for review. I managed to get it all on a single line of code! No, that one line has like 5000 characters, why do you ask?
Nobody is asking the question "If you have to use AI that much, doesn't that mean you aren't very good at your job? 🤔"
I'm asking it all the time, but now only the AI will talk to me...lol.
Right? How do you even cheat on a ruleset this dumb? You don‘t. It was a stupid contest from the start.
If they're ranking you based on AI usage, they're going to use that when they make decisions about raises and promotions. It may be a stupid contest but the employees are part of it whether they like it or not.
You can bet your ass I'd be trying to pad my numbers.
By not promoting the people on top of the ranking who can't do things without AI and waste a lot of resources, right?
...right?
Well they do stack ranking. The promotions are not guaranteed, but the firings for people at the bottom of the leaderboard are.
It only makes sense if
I can imagine leadership - disconnected from real work and any practical AI use experience - being misinformed and misguided into believing marketing and hype-cycle about gains. It also doesn't seem implausible that leadership wants to drive up adoption to quickly gain feedback and results about usefulness and gains/loss.
In good faith, it requires a certain mindset (no care about the waste or potential loss or risk) and distance from practice. Not implausible, though, in my eyes.
This is all the explanation you need on why they're doing this bone headed shit. It's not their problem in a few quarters when they jump ship after padding their resume on the company's dime.
Sure. But I haven't seen credible evidence that any of this drove any revenue.
Correct features, thoughtfully planned, and expertly executed, at the right time, sometimes drive new revenue.
AI slop is about 99% orthogonal to anything that helps drive revenue.
People will claim it helps with timing, but timing only works if the feature is correct and AI makes organizations that rarely got things correct in the first place even less likely to get things correct.
Like judging how good a driver is by the person with the longest distance a to b.
I mean I can say it's not quite as guaranteed to be bad. IE distance from A to B is inherently bad, Most distance driven COULD mean you made more stops and did more good.... or it could mean you took a horrible route, got lost and wound up crossing through the wrong state.
We don't need a map to guide us.
Should it be snowing?
Hey, I've never seen the sun come up in the West?!
And here we have our employee of the year! He accidentally turned left instead of right, and ended up circumnavigating the entire globe. While most of you only use 2 miles to go from A to B, he used 24899. Isn’t that incredible?
I used 5 AI.
I used 2 AI before i used 2 AI, then i used 2 AI some more...
I mean miles driven is at least proportional to amount of useful work, more miles is more distance they've transported cargo. The AI usage leaderboard is useless.
No, because you can keep making circles around the hq. Miles go up, not useful at all.
Only if you assume that all miles are correctly headed towards the destination. 2 drivers are given the same 3 places to deliver packages to.
one drives 2000 miles, the other 50.
Admitted though now that I actually think about it, I guess we already have that level of stupid assumptions. After all the normal system of pay for many jobs is by the hour. Which I suppose has all the same flaws.
Yes! It does. I felt that I had to get out of hourly billing consultancy programming, because I code so fast I would have gone broke.