@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

"they claim they can't do any work at all." Saying something like I can't do this terrifies me, as it says Im incompetent and should not be filling that position. Besides that this doesn't provide any information for others to give me help which I desperately need.

That's why I try to say what I want to acomplish, what I hove done, and what's the issue, and thanks to that half the time I get new ideas to check and maybe even I get to solve my problem.

@drikanis
Thanks for this comment. It made something click for me -- token limits for developers are probably a good thing. It's a built in signal to take a break and step back from their work for a minute. Do some planning, reading, or writing, or just go stretch your legs.
This problem is not specific to LLM-assisted programming. There's always a risk of tunnel vision in the desire to get more done, and failing to establish foundations and context for the product.

@jablkoziemne @ludicity