> We don't see the debugger output and go "how do I make this bad output go away?!?"

In the past, I've worked with developers that do. You ask them to investigate and deal with an error message, and all they do is whatever makes the error go away. Oh, a null pointer exception is thrown? Lets wrap it in a try/catch and move on.

▲

pc86 6 days ago | parent | next [-]

If you haven't worked with someone who you honestly think may have a severe learning disability or outright brain damage, you just haven't been working professionally for long enough.

	▲	coldtea 6 days ago \| parent [-]
		And now we can automate severe learning disability or outright brain damage with LLMs! Yay!

▲

blauditore 6 days ago | parent | prev | next [-]

Or google the error message, click first link, blindly copy-paste whatever code snippet comes up and re-run code/test.

Yes, such workflows (jobs or) may become obsolete with some of the modern AI tools. Is that a bad thing? Not sure...

▲

uoaei 6 days ago | parent | prev | next [-]

Hiring bad engineers will always be a problem, even (especially) in the age of LLMs.

▲

tyleo 6 days ago | parent | prev | next [-]

Agreed. I’d argue there can be a time and place for it but reaching for it as the default tool on the shelf is a hallmark of incompetence.

▲

rafaelmn 6 days ago | parent | prev [-]

Thankfully those developers are now interchangeable with LLM agents.