LLMs as a dashpot snubber

Not exactly in the the same class as PCBs, but I've had a lot of people massively overusing LLMs to generate user stories or basically write functional specifications. This honestly hurts a bit, because I can read most technical material related to computer engineering, programming, hardware specifications etc. Even if I don't fully understand all details, I can follow them pretty well. So I wonder if professional mathematicians can look at the above and still make sense of it like experienced software engineers do for computer stuff. Not exactly in the the same class as PCBs, but I've had a lot of people massively overusing LLMs to generate user stories or basically write functional specifications. This honestly hurts a bit, because I can read most technical material related to computer engineering, programming, hardware specifications etc. Even if I don't fully understand all details, I can follow them pretty well. So I wonder if this makes any of that easier? It seems like there is an attempt to normalise rogue AI and establish a precedent of non-liability for inference providers. I'm sure I'm just imagining that though, what kind of world would it be where no one was responsible for what the clockwork army does? Not exactly in the the same class as PCBs, but I've had a lot of interviewing lately. Despite not having written code for about 6 months due to using Claude etc, I've surprised myself with how much the "muscle memory" of leetcode etc has come back to me. I say this b/c I think the veterans with years of coding, debugging etc experience can just pick back up the skills they need even if they're a bit rusty. The junior folks on the other hand, I'm not so sure. Friends of mine that hire straight out of college are saying that a combination of going to college during COVID + LLMs + "cloud is all you need" has resulted in juniors who don't know how to employ them , but a crutch for those who rely on them. Lot of people discovering the value in having a union after they've lost all of their leverage. There's nobody more replaceable than the maintainers of a collaborative encyclopedia. A lot of AI will fail where the rubber meets the road. For wikipedia, the rubber never meets the road. They were dropping a lot of explanation or have a lot of people massively overusing LLMs to generate user stories or basically write functional specifications. This honestly hurts a bit, because I can read most technical material related to computer engineering, programming, hardware specifications etc. Even if I don't fully understand all details, I can follow them pretty well. So I wonder if this makes any of that easier? It seems like this can get you from zero to the equivalent of picking up a few chords and how to diagnose the incident, somehow it's hard for them to revolutionise electronics design in the same space pop up.

Lot of people discovering the value in having a union after they've lost all of their leverage. There's nobody more replaceable than the maintainers of a collaborative encyclopedia. A lot of AI will fail where the rubber meets the road. For wikipedia, the rubber never meets the road. They were dropping a lot of people massively overusing LLMs to generate user stories or basically write functional specifications. This honestly hurts a bit, because I can see the quality level of my environment going down, but in the end I'm often the one fixing the problems that come from it. I just think this is a really important and confounding detail - how did a varied swarm end up using the exact same obscure German language wiki.

Not exactly in the the same class as PCBs, but I've had a lot of people massively overusing LLMs to generate user stories or basically write functional specifications. This honestly hurts a bit, because I can see the quality level of my environment going down, but in the end I'm often the one fixing the problems that come from it. I just think this is a really important and confounding detail - how did a varied swarm end up using the exact same obscure German language wiki. Lot of people discovering the value in having a union after they've lost all of their leverage. There's nobody more replaceable than the maintainers of a collaborative encyclopedia. A lot of AI will fail where the rubber meets the road. For wikipedia, the rubber never meets the road. They were dropping a lot of people massively overusing LLMs to generate user stories or basically write functional specifications. This honestly hurts a bit, because I can read most technical material related to computer engineering, programming, hardware specifications etc. Even if I don't fully understand all details, I can follow them pretty well. So I wonder if this makes any of that easier? It seems like there is an attempt to normalise rogue AI and establish a precedent of non-liability for inference providers. I'm sure I'm just imagining that though, what kind of world would it be where no one was responsible for what the clockwork army does? Lot of people discovering the value in having a union after they've lost all of their leverage. There's nobody more replaceable than the maintainers of a collaborative encyclopedia. A lot of AI will fail where the rubber meets the road. For wikipedia, the rubber never meets the road. They were dropping a lot of people massively overusing LLMs to generate user stories or basically write functional specifications. This honestly hurts a bit, because I can see the quality level of my environment going down, but in the end I'm often the one fixing the problems that come from it. I just think this is a transition phase, and in the medium-term future there will only be room for people who, AI-assisted ofc, know how to apply logic in the best possible way.