@ludicity I work in infra rather than software, and yeah. When I started, we joked that half the job was reading logs and the other half is copypasting those logs into stackoverflow and serverfault to find fixes.

There's always been the occasional person who comes on board who is a liability rather than an engineer, but they generally did not stay long.

Now there's a small but significant number of people who don't read past the google AI box. If that doesn't fix it, they don't seem to know where else to look.

Part of that is absolutely down to corporate culture having KPIs for response time and tickets per day, but not directly measuring or rewarding fixes. So there's a strong incentive to rush to hit those measuring sticks before digging in to spend time learning.

Part of it is definitely that the AI reply is the first thing google shows and it sometimes works. Kinda like how a slot machine sometimes pays out.