In my experience it is now twice the amount of merge requests as a follow-up appears to correct any bugs no one reviewed in the first merge request.

▲

silentkat 21 hours ago | parent [-]

I’m at a big tech company. They proudly stated more productivity measures in commits (already nonsense). 47% more commits, 17% less time per commit. Meaning 128% more time spent coding. Burning us out and acting like the AI slop is “unlocking” productivity.

There’s some neat stuff, don’t get me wrong. But every additional tool so far has started strong but then always falls over. Always.

Right now there’s this “orchestrator” nonsense. Cool in principle, but as someone who made scripts to automate with all the time before it’s not impressive. Spent $200 to automate doing some bug finding and fixing. It found and fixed the easy stuff (still pretty neat), and then “partially verified” it fixed the other stuff.

The “partial verification” was it justifying why it was okay it was broken.

The company has mandated we use this technology. I have an “AI Native” rating. We’re being told to put out at least 28 commits a month. It’s nonsense.

They’re letting me play with an expensive, super-high-level, probabilistic language. So I’m having a lot of fun. But I’m not going to lie, I’m very disappointed. Got this job a year ago. 12 years programming experience. First big tech job. Was hoping to learn a lot. Know my use of data to prioritize work could be better. Was sold on their use of data. I’m sure some teams here use data really well, but I’m just not impressed.

And I’m not even getting into the people gaming the metrics to look good while actually making more work for everyone else.

▲

booleandilemma 19 hours ago | parent | next [-]

Management is just stupid sometimes. We had a similar metric at my last company and my manager's response was "well how else are we supposed to measure productivity?", and that was supposed to be a legitimate answer.

	▲	sdf2df 6 hours ago \| parent [-]
		The benefits of AI either accrue toward incremental revenue-generation or cost-saving. Its not rocket science to measure actually. The issue is most people dont know how to think properly to invent the right proxies.

▲

sdf2df 21 hours ago | parent | prev [-]

Lol its gonna take longer than it should for this to play out.

Sunk cost fallacy is very real, for all involved. Especially the model producers and their investors.

Sunk cost fallacy is also real for dev's who are now giving up how they used to work - they've made a sunk investment in learning to use LLMs etc. Hence the 'there's no going back' comments that crop up on here.

As I said in this thread - anyone who can think straight - Im referring to those who adhere to fundamental economic principles - can see what's going on from a mile away.