Software Engineers: Do you honestly get anything useful out of LLMs?
Summary
A software engineer expresses frustration with local LLMs for agentic coding, citing issues like technical debt, ignored instructions, and excessive code generation, questioning their usefulness.
Similar Articles
LLMs are eroding my software engineering career and I don't know what to do
A software engineer with 10 years of experience in finance and payment systems reflects on how LLMs like ChatGPT and Claude are eroding the value of his domain-specific knowledge, as AI can now handle complex design tasks that previously required years of expertise.
Software engineering best practices in the age of LLM coding
An article discussing how software engineering best practices are evolving with the integration of LLM-based coding tools, offering guidance for developers.
@msimoni: So far, I haven't been able to make LLMs significantly help me with the hard parts of programming - designing code that…
The author finds that LLMs are not significantly helpful for the hard parts of programming (designing simple, general, clear code) but are so helpful for other parts that they rate them as a 10x productivity improvement.
Effective use-cases for LLMs
This article shares practical, real-world use cases for LLMs in software engineering, including searching through customer conversations via RAG, triaging API failures from logs, and shortening content. It emphasizes efficiency gains and reducing manual sifting.
LLMs are bad at vibing specifications
Hillel Wayne discusses how LLMs, while popular for writing formal specifications like TLA+ and Alloy, often produce shallow, tautological properties that fail to capture subtle bugs, based on analysis of community projects.