> Assuming at least that you are an otherwise competent developer and that you carefully review all code before you commit it. That is a big assumption. If eve

> Assuming at least that you are an otherwise competent developer and that you carefully review all code before you commit it. That is a big assumption. If everyone were doing that, this wouldn’t be a major issue. But as the curl developer has noted, people are using LLMs without thinking and wasting everyone’s time and resources. https://www.linkedin.com/posts/danielstenberg_hackerone-curl-activity-7324820893862363136-glb1 https://www.linkedin.com/posts/danielstenberg_hackerone-curl... I can attest to that. Just the other day I got a bug report, clearly written with the assistance of an LLM, for software which has been stable and used in several places for years. This person, when faced with an error on their first try, instead of pondering “what am I doing wrong” instead opened a bug report with a “fix”. Of course, they were using the software wrong. They did not follow the very short and simple instructions and essentially invented steps (probably suggested by an LLM) that caused the problem. Waste of time for everyone involved, and one more notch on the road to causing burnout. Some of the worst kind of users are those who think “bug” means “anything which doesn’t immediately behave the way I thought it would”. LLMs empower them, to the detriment of everyone else.