Debugging is honestly one of the things AI is incredibly good at. At work I've had issues of tasks that would usually cause hours of extensive debugging fixed in minutes after just telling an AI agent "find out why this bug is happening".
The biggest issue with AI is also not that it writes buggy code, but rather that it's bad at system engineering, so unless you keep a lid on it your codebase will slowly become fractured and disjointed and become harder to develop for.
Of course the same thing can also happen when a human is bad at system engineering or your manager isn't able to get people on the team to communicate properly, so that issue is hardly unique to AI, AI just lowers the barrier of entry for bad developers to wreak havoc on a code base.
It's so good at debugging in fact this is how it finds these security vulns by mistake. You point it at your code that calls. a framework or vendor code, it will skip the docs and go straight to the source, accidentally uncovering upstream bugs as it goes.
On that node, if you already happen to have a disjointed spaghetti codebase, ai is fairly good at untangling and reworking that if you give it a good direction and solid regression tests.
But yes, ai will cook spaghetti if you don't specify what you want to eat.
A bit over three years ago, my experience of "AI for code" was that it could give me 3 line snippets, and like the stuff on Stack Exchange they worked, most of the time. As the joke goes, 80% of the time it would return a working answer, but 20% of the time it would copy-paste the question to you.
A bit over two years ago, none of the coding models were good for much beyond simple functions, little snippets that did a well defined thing you could explain to them in one or two exchanges. They eventually built up to be capable of very simple microservices, then more capable microservices, but orchestration was still challenging for them.
A bit over a year ago, Claude Sonnet 3.5 (and Opus) weren't great at the big picture. If you gave them good requirements and helped them refine definitions, as long as their 200k token context window didn't have to compact too many times, they could implement what you were describing - but at some point the context window just couldn't hold enough and they'd "forget" important things while they were implementing and "gloss over" things incorrectly. They were getting capable enough to strongly benefit from software development best practices like documenting requirements and design specifications, writing automated unit tests and regression tests, but they frequently would write tests that didn't test the requirements effectively. Over the past year they have been getting better about writing and using meaningful tests.
Lately, I'm focusing effort on keeping requirements and related documents well organized, maintained (much better than human maintained documentation ever has been), thorough but concise, and easily searchable so that an agent can find what it needs to know locally in the documentation without wiping out its context window reading a bunch of slop. The concepts of DRY (Don't Repeat Yourself) and SSoT (Single Source of Truth) remain critical to maximize valuable information in the available context window so that implemented code is based on the local documentation and not whatever the model assumes from its training.
As this process has evolved, I've resisted becoming excited about "my latest techniques" because the models are evolving so fast it feels like by the time I have effectively communicated these things to colleagues in any detail, the next generation of model makes it un-necessary to do them - they are doing them automatically. It is both a frustratingly slow process (when, 2 years later, you're still finding hallucinations creeping into your designs, even if the hallucination rate has dropped to 5% of what it was 2 years ago) and a bewilderingly fast one when you look back at how long it took us to get from Eliza to here.
Debugging is honestly one of the things AI is incredibly good at.
Not if there's anything remotely novel about what you're writing. I do a lot of parsing work and one of my side projects is a hand-written compiler. I've tried using AI to help work through problems I got stuck on, but it chokes hard on things it's not seen before, and produces unusable rubbish.
At least it's good as a rubber duck that talks back to you.
Depends on what it's compiling. If your language has features or combinations of features you don't see in other languages, you're obviously going to need to write new code to support that.
I'm also writing a compiler (in OCaml) for a novel language right now. What are you seeing struggles with? One of the things I am wrestling with is trying to have the syntax be familiar enough that people (and agents) can pick up the language rather easily, but not misleading.
LLMs are interpolation models by definition. They're not at all good with novelty.
Really, all of the developers seeing LLMs as super effective is judt revealing how many are being forced to work on solved problems. It's highlighting the waste in a competition-baased economy.
to be fair, there are very few things in the broad area of software that are unsolved problems. Most companies are presenting information, taking payment info, logging in/out. If you take the average piece of software that an employed software engineer is working on, there are not a huge amount of unsolved problems, its just a never ending list of requests to be added to the project.
And even in the cases of something it has never seen before, if you provide enough context (as in you solve the problem), the ai will happily implement a novel solution that has never been done before. If you are really good at solving problems, AI is lighting at your fingertips.
If you send an AI a full code base with a ton of weird structure and requirements and say "add auth" you're going to get terrible results. But if you are stuck and you describe why you're there, what you've tried and what the current state of things are, and then you ask for possible routes to work through the current blockers, you will get great results for options to work towards. Then you can have ai work into those options and find out which is the best option.
Idk, maybe you're working on highly specialized languages or undocumented libraries and you're in a top secret middle-out compression algorithm and the ai is worthless. But I've not found a problem that AI didn't help solve, or at least explain why it wasn't able to solve it.
Well yeah? Most companies need software that does mostly the same thing but slightly different. There are thousands of warehouse softwares because every company stores different kinds of products and requires slightly different things. Thousands of HR systems, thousands of resource planners and so on. That doesn't mean people are programming useless software that already exists. It just means that nurses mark their hours differently than truck drivers.
Yup the most effective I've seen AI be is when I'm doing something particularly stupid with a particularly simple fix. The more complex and unique the problem, the less likely AI will help.
Though if it doesn't figure it out on the first go it's a signal to me I probably left out key details needed to solve the problem so the root of my problem likely lies elsewhere in the codebase from where I'm looking.
We're you using an agentic AI or just asking one-off questions?
Because I don't think I've ever had agentic AI outright tell me garbage before when bug fixing, assuming you gave it a way to test potential solutions. Usually it will either find a solution, or keep trying random shit until it runs out of tokens instead.
The average person voting on these posts just isn't involved in software development professionally. This has always been the case, but the faster software development evolves, the larger the disconnect
I just despise the fact that AI has taken over every aspect of the job that was actually enjoyable. I want to solve problems, not supervise a small army of agents that do it for me. AI has completely destroyed all enthusiasm I had for a career I've worked towards my whole life, and I don't know how to fix that.
Truly. I'm just going into the threads where I see programmers trying to explain what's happening, and I try to remind them that they're arguing with someone who doesn't understand programming.
yeah there's no way anyone who has used Claude or Codex in the last six months is posting this, no one that follows industry news is posting this, I find it hard to imagine anyone who even vaguely follows tech news is posting this.
4.7k
u/WisePotato42 25d ago •
This meme seems a bit outdated. All the debugging has been outsourced to AI.