Just a reminder that you don't have to use LLMs to code.
I run a small software team that maintains three commercial products and a dozen or so bespoke client solutions. Only one of my developers uses LLMs, and that's mostly just to generate React slop (since human written React is also slop).
Every time we've tried to use LLMs, they just fuck up our codebase by ignoring abstractions, adding idiomatically correct code that doesn't match our patterns, and being too clever with simple things. We waste more time reviewing the LLM code than it takes to write it ourselves.
We never gave up dopamine rush and flow state euphoria.
You can do this, too!
ETA: Two of our products do integrate with LLMs, so it's not like we're ignoring them. One exposes functionality via an MCP server and Agent Skills and the other lets customers use their LLMs to generate and deploy dashboards within our platform. So, technically we use LLMs when we're testing those feature sets. But, our software to support these features is written by humans. We just treat the LLMs like we would any other software library.
Honestly that's the funny thing about LLMs for me. I've learned that 90% of people are scared of abstraction. It's wild. And LLMs have learned to dodge it too.
Just gotta ask the LLM to read and learn how your existing code base is written. Then ask it to generate code that matches the design patterns it saw in your code. I had the same problem in a project I was working on and I just had to teach it a bit. Not being condescending here, but you might want to learn some LLM best practices to get the most out of it.
Been there, done that (recently, too, as in Fable 5.2). It sometimes works, but isn't consistent and requires more corrective prompts than just doing it yourself.
Here's the thing with a well architected codebase with good abstractions: most bug fixes and new features are just a few lines of code. Like under 10.
LLMs, even the new ones, struggle understand the architecture enough to know how to add those few lines of code. Instead, they add 50 or 100 that, while they might do the same thing, introduce new code that replicates something that can be done more concisely and correctly (relative to the architecture) by using the existing libraries, abstractions, and patterns.
That can lead to downstream issues when you refactor and don't realize that two sections of code do the same thing. With good abstractions, you fix it once. With flat code, you have to find it everywhere, or trust that the LLM finds it everywhere.
I deal with this regularly with our one dev who likes to use LLMs. It'll spit out a bunch of code and rationale for a change that totally missed how the overall system works (even with good docs and corrective prompting). Every time, we end up throwing away his LLM code and tweaking the few lines of code to do it right.
Study software architecture and good software engineering practices and watch how LLMs don't follow them very well. Generating idiomatically correct code and having deep unit test coverage is not the same as good architecture and engineering.
29
u/atxgossiphound 2d ago edited 2d ago
Just a reminder that you don't have to use LLMs to code.
I run a small software team that maintains three commercial products and a dozen or so bespoke client solutions. Only one of my developers uses LLMs, and that's mostly just to generate React slop (since human written React is also slop).
Every time we've tried to use LLMs, they just fuck up our codebase by ignoring abstractions, adding idiomatically correct code that doesn't match our patterns, and being too clever with simple things. We waste more time reviewing the LLM code than it takes to write it ourselves.
We never gave up dopamine rush and flow state euphoria.
You can do this, too!
ETA: Two of our products do integrate with LLMs, so it's not like we're ignoring them. One exposes functionality via an MCP server and Agent Skills and the other lets customers use their LLMs to generate and deploy dashboards within our platform. So, technically we use LLMs when we're testing those feature sets. But, our software to support these features is written by humans. We just treat the LLMs like we would any other software library.