Reposting a question for Ed Zitron, I'll forward responses.
-
@ludicity Depends. Rarely professionally, but I did most of my hiring for most of my life and I’ve seen things you people wouldn’t believe during the interviews.
The worst people were exactly like LLM - stupid, loud and unable to admit they are wrong.
-
-
Reposting a question for Ed Zitron, I'll forward responses. He asked on Bluesky and will get sub-Mastodon-tier answers:
"This is a serious question and I would be delighted if I only hear great things but, software engineers: both before and after LLMs, how often in your professional lives have you run into software engineers that seem completely useless or lacking in basic knowledge? I hope the answer is rarely"
@ludicity i don't quite know how to tell ed that, like basically every other field of endeavor, software is permeable to people who have no useful idea what they're doing.
(or, i guess, that some of the people who lack basic knowledge and have no ability to contribute will probably stay that way forever but that many others eventually figure things out and become pretty effective.)
-
Reposting a question for Ed Zitron, I'll forward responses. He asked on Bluesky and will get sub-Mastodon-tier answers:
"This is a serious question and I would be delighted if I only hear great things but, software engineers: both before and after LLMs, how often in your professional lives have you run into software engineers that seem completely useless or lacking in basic knowledge? I hope the answer is rarely"
@ludicity 10 years in data engineering. "Completely useless" is something I've only seen a few times, more often in non-technical managers which wasn't the question.
I do often see engineers who don't understood best practices or good architecture. Or don't understand the frameworks they are using. Or frankly just don't try.
The LLM spell mostly affects the beginner or mediocre engineer. Senior engineers find them mostly frustrating but occasionally useful.
-
@ludicity For the record, I work at a software company that employs ~10k developers.
Before LLMs, I'd encounter such engineers a couple of times a month, but I interact with a lot of engineers, specifically the ones that need help or are new at the company or industry at large, so it's a selected sample. Even the most inexperienced ones are willing and able to learn with some guidance.
After LLMs, there's been a significant uptick, and these new ones are grossly incompetent, incurious, impatient, and behave like addicts if their supply of tokens is at all interrupted. If they run out of prompt credits, its an emergency because they claim they can't do any work at all. They can't even explain the architecture of what they are making anymore, and can't even file tickets or send emails without an LLM writing it for them, and they certainly lack in any kind of reading comprehension.
It's bleak and depressing, and makes me want to quit the industry altogether.
-
@ludicity For the record, I work at a software company that employs ~10k developers.
Before LLMs, I'd encounter such engineers a couple of times a month, but I interact with a lot of engineers, specifically the ones that need help or are new at the company or industry at large, so it's a selected sample. Even the most inexperienced ones are willing and able to learn with some guidance.
After LLMs, there's been a significant uptick, and these new ones are grossly incompetent, incurious, impatient, and behave like addicts if their supply of tokens is at all interrupted. If they run out of prompt credits, its an emergency because they claim they can't do any work at all. They can't even explain the architecture of what they are making anymore, and can't even file tickets or send emails without an LLM writing it for them, and they certainly lack in any kind of reading comprehension.
It's bleak and depressing, and makes me want to quit the industry altogether.
@drikanis @ludicity The writing was on the wall when front end developers stopped being able to do anything if there wasn't already a component in a library somewhere they could import.
"Can we have that as a drop down list with an icon next to each item?”, I say.
"No”, they say, “I don't think our framework has that”
-
@ludicity Ask me how many times someone other than me has, in my presence, used or mentioned using a debugger (As contrary to inserting a bunch of debug prints in the code).
Zero. It’s zero times.
-
@ludicity For the record, I work at a software company that employs ~10k developers.
Before LLMs, I'd encounter such engineers a couple of times a month, but I interact with a lot of engineers, specifically the ones that need help or are new at the company or industry at large, so it's a selected sample. Even the most inexperienced ones are willing and able to learn with some guidance.
After LLMs, there's been a significant uptick, and these new ones are grossly incompetent, incurious, impatient, and behave like addicts if their supply of tokens is at all interrupted. If they run out of prompt credits, its an emergency because they claim they can't do any work at all. They can't even explain the architecture of what they are making anymore, and can't even file tickets or send emails without an LLM writing it for them, and they certainly lack in any kind of reading comprehension.
It's bleak and depressing, and makes me want to quit the industry altogether.
-
@ludicity For the record, I work at a software company that employs ~10k developers.
Before LLMs, I'd encounter such engineers a couple of times a month, but I interact with a lot of engineers, specifically the ones that need help or are new at the company or industry at large, so it's a selected sample. Even the most inexperienced ones are willing and able to learn with some guidance.
After LLMs, there's been a significant uptick, and these new ones are grossly incompetent, incurious, impatient, and behave like addicts if their supply of tokens is at all interrupted. If they run out of prompt credits, its an emergency because they claim they can't do any work at all. They can't even explain the architecture of what they are making anymore, and can't even file tickets or send emails without an LLM writing it for them, and they certainly lack in any kind of reading comprehension.
It's bleak and depressing, and makes me want to quit the industry altogether.
-
Reposting a question for Ed Zitron, I'll forward responses. He asked on Bluesky and will get sub-Mastodon-tier answers:
"This is a serious question and I would be delighted if I only hear great things but, software engineers: both before and after LLMs, how often in your professional lives have you run into software engineers that seem completely useless or lacking in basic knowledge? I hope the answer is rarely"
@ludicity I'm pretty sure a bunch of my coworkers are incompetent and/or disinterested, myself included, but our engineering job is so braindead that it doesn't matter much.
Anyone can take some json event and send it off to a different event. I think many of us would count as incompetent in a less stupid environment. So the answer is "all the time, probably?"But we also barely hired anyone since the LLM boom so maybe I'm lacking the floor comparison.
-
@arichtman @ludicity it's worse, but it was always bad
-
@arichtman @ludicity like the old gag goes:
How many people do you have working for you?
About 50% -
@Patrickoldhiker @drikanis @ludicity Amen to that. The fact that I'm so close to retirement is a great source of comfort to me. Yeah, I enjoy my job, and I know I'm good at it. I do not need to use an LLM for anything.
But should I get that dreaded conversation tomorrow and a disappointing redundancy package, it would no longer be a cause for concern.
-
Reposting a question for Ed Zitron, I'll forward responses. He asked on Bluesky and will get sub-Mastodon-tier answers:
"This is a serious question and I would be delighted if I only hear great things but, software engineers: both before and after LLMs, how often in your professional lives have you run into software engineers that seem completely useless or lacking in basic knowledge? I hope the answer is rarely"
@ludicity Rarely proportionately, frequently absolutely.
-
@Patrickoldhiker @drikanis @ludicity Amen to that. The fact that I'm so close to retirement is a great source of comfort to me. Yeah, I enjoy my job, and I know I'm good at it. I do not need to use an LLM for anything.
But should I get that dreaded conversation tomorrow and a disappointing redundancy package, it would no longer be a cause for concern.
@rozeboosje @Patrickoldhiker @drikanis @ludicity I'm seeing this comment a lot (and I would feel the same were I closer to retirement). LLMs are pushing knowledge and experience out of the workforce and replacing it with vibes.
-
Reposting a question for Ed Zitron, I'll forward responses. He asked on Bluesky and will get sub-Mastodon-tier answers:
"This is a serious question and I would be delighted if I only hear great things but, software engineers: both before and after LLMs, how often in your professional lives have you run into software engineers that seem completely useless or lacking in basic knowledge? I hope the answer is rarely"
@ludicity I've done technical interviews of 100+ candidates for software engineering roles over the years. Around 90% of them didn't pass muster. And that's after a CV screening by HR (for whatever that's worth) and a preliminary interview with a teamlead.
It is RIDICULOUS how many career programmers are, in fact, not able to program anything in their language of choice. I'm not talking about having to google how to open a socket, but about how to write a god damned loop ... Awful incompetence.
-
@ludicity I've done technical interviews of 100+ candidates for software engineering roles over the years. Around 90% of them didn't pass muster. And that's after a CV screening by HR (for whatever that's worth) and a preliminary interview with a teamlead.
It is RIDICULOUS how many career programmers are, in fact, not able to program anything in their language of choice. I'm not talking about having to google how to open a socket, but about how to write a god damned loop ... Awful incompetence.
@ludicity Maybe these people have other qualities that I didn't screen for in my interviews. Maybe LLMs will let those qualities shine through.
But secretly, the cynic in me thinks this is going to be garbage in, garbage out, only at a hitherto unseen scale.
-
@ludicity For the record, I work at a software company that employs ~10k developers.
Before LLMs, I'd encounter such engineers a couple of times a month, but I interact with a lot of engineers, specifically the ones that need help or are new at the company or industry at large, so it's a selected sample. Even the most inexperienced ones are willing and able to learn with some guidance.
After LLMs, there's been a significant uptick, and these new ones are grossly incompetent, incurious, impatient, and behave like addicts if their supply of tokens is at all interrupted. If they run out of prompt credits, its an emergency because they claim they can't do any work at all. They can't even explain the architecture of what they are making anymore, and can't even file tickets or send emails without an LLM writing it for them, and they certainly lack in any kind of reading comprehension.
It's bleak and depressing, and makes me want to quit the industry altogether.
-
Tangential, I have noticed a trend with customer emails (wide spread, many multiples companies) that makes me believe more people are using LLMs to write reply emails & not reading at all.
there's a 'jje ne sais quoi' to not just them not answering questions but *how* they're not answering questions.
I can't put my finger on it, but it's tripping my spidy-sense / pattern recognition.
-
Reposting a question for Ed Zitron, I'll forward responses. He asked on Bluesky and will get sub-Mastodon-tier answers:
"This is a serious question and I would be delighted if I only hear great things but, software engineers: both before and after LLMs, how often in your professional lives have you run into software engineers that seem completely useless or lacking in basic knowledge? I hope the answer is rarely"
@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.
