Software Engineers: Do you honestly get anything useful out of LLMs?

Reddit r/LocalLLaMA News

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.

For 6 months now I've been trying to make agentic coding work for me, using Pi and a handful 30-120B models (Qwens, Nemotrons, Leguna...etc). I'm not greedy either, I stick to decent quants, never quantize kv cache, and keep my sessions up to 90k max. But the results have ALWAYS been disappointing. No matter how much you harness the model or bombard it with pages-worth of markdown instructions, the agents continue to add technical dept more than value. And I end up spending more time cleaning up mess than I would've spent on doing everything by hand at the first place. I mean those models are absolutely shameless: They'll repeat themselves badly. They'll totally abandon what methodology you specify (eg functional-programming vs object-oriented) if they happen to be more comfortable with the other. Blatantly ignore instructions at 50k+ depth of context. Write superficial tests that pass easily, just to pat themselves on the back. Almost never stop for a moment to think they could refactor a mess before piling code on top of it. They all tend to write a shit ton of code that I always find myself reaching for ctrl+c before I get a heart attack! A junior engineer worth his salt wouldn't be that messy. And at the end of the day, there's a limit to how much architecting and steering one could do, before it turns into a micro-management hell. So, for the Senior Engineers that witness an increase in productivity thanks to agentic coding (as I always hear), how exactly do you do it? Thanks! Edit: Sorry. I meant to refer to local models. I thought this is LocalLLama.
Original Article

Similar Articles

Effective use-cases for LLMs

Lobsters Hottest

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 — Computer Things

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.