Ask HN: If AI Tools Are So Good, Why Isn't Your Bug Backlog Empty?

I often get asked by people outside tech whether AI will replace programmers. My thought is: if that were true, we should be running out of things to do—the bug backlog should be empty and we'd have caught up on every feature request from PMs, to the point of being bottlenecked on the business side. But that's not the case at my company or for most devs I talk to. So what gives?

I don't know if I'm doing something wrong but bug fixing with AI has always been a crapshoot. You can absolutely tell an agent to fix an issue, and it will fix that issue, but the vast majority of the time that solution will be by adding code to cover the specific symptom in the bug report. It rarely considers or recommends solutions that have tradeoffs that may change behavior but will eliminate an entire class of similar bugs. This is mostly a problem of agents not having the autonomy of managing an entire project and having the ability to make tradeoffs to increase simplicity or maintainability, but when given that autonomy no AI model I've used uses that privilege to write simpler, more maintainable code.
It makes me wonder if it could be solved with better context management. A real developer builds up global context of the whole project over time, you always hold the overall architecture in your head. Whereas with agents there is still a lot lost between sessions. It's similar in a sense that a new developer to a project does more hacky local solutions whereas the senior on the team knows when the architecture needs to change as part of a fix.
Mine is. I've been telling my senior management that it's cheaper to rewrite stuff from scratch with AI than fix OLD products. They ate that up and everything we have now never reach v1.0 status.
It is empty, for me and my team (I'm an engineering manager). We still have a support rotation but it's just so someone is aware they're supposed to respond to any alerts that come up. Edit: product doesn't have a deep backlog either. Usually we can only plan somewhere between a couple days and a month in advance. Major recent product launch so we are longest-horizon we have been for a while.
I can confirm the same, backlog is sort of empty unless we try to attack a new domain, and that's usually a 2-3 month party, after that you need to almost imagine tasks. This really smells like end of backlog situation to me.
  1. frostiness

    I don't know if I'm doing something wrong but bug fixing with AI has always been a crapshoot. You can absolutely tell an agent to fix an issue, and it will fix that issue, but the vast majority of the time that solution will be by adding code to cover the specific symptom in the bug report. It rarely considers or recommends solutions that have tradeoffs that may change behavior but will eliminate an entire class of similar bugs.

    This is mostly a problem of agents not having the autonomy of managing an entire project and having the ability to make tradeoffs to increase simplicity or maintainability, but when given that autonomy no AI model I've used uses that privilege to write simpler, more maintainable code.

  2. td521534f12

    All my solo project backlogs _are_ empty.

    For my team projects, I still need my teammates to review code, so that bottlenecks how quickly we can burn down the backlog. If I didn't need code review I would have the backlog burned down in weeks, but I'd create a bunch of outages in the process (we do catch things in code review!)

    Also, some of my solo projects are gamedev-related, and gamedev is also bottlenecked on actually playing your game to see if its fun :) but it is great to get out of a 2 hour playtest session with notes and have a new build in like 15 minutes with the feedback incorporated.

  3. fishtoaster

    It pretty much is? Every easily-described bug has been fixed. The only things that remain are "this isn't wrong per se, it just violates customer expectations" and someone needs to figure out what the product should do in this case.

    We burnt through our backlog of "obviously we should do this when we have time" stuff in the spring. It was pretty fun to kill pretty much all of my multi-year refactor and cleanup list.

    Now we are pretty much bottlenecked on the business side.

  4. GuB-42

    Because AI is better at finding bugs than at fixing them.

    It is not good at writing bug-free code either.

    AI and humans don't make the same bugs. So AI may find bugs that are easily overlooked by humans while at the same time being incredibly stupid on some other parts.

  5. mattbrewsbytes

    If your team and product had a large backlog before thats not going to change. AI tools amplify whatever it is you do so if you've been ignoring bugs and focusing most of the time on new features, AI isn't going to magically change what a team is working on.

    On a technical level, take your average NullPointerException or the equivalent in whatever language you use. Ask AI to go fix it and it will sanely wrap or check for nulls in that piece of code. Ask a lead or senior engineer to fix it and they will (hopefully) start with "why is this data null? it shouldn't be" and then trace back through logs or data, try to recreate with a real scenario and not only fix that bug but find there's an unhandled scenario somewhere else in the code base. Someone could prompt the AI to expand further and do a root cause analysis but do you trust it to find things and fix them properly?

  6. yokuze

    > The bug backlog should be empty

    I don't follow.

    Maybe it's just me, but I've never worked at a company and on any substantial product that had an empty bug backlog. If a bug queue is empty, the product is either not used much (or not a priority), not tested well enough, or not monitored enough.

    I don't know that a world where AI has mostly replaced programmers is a world with an empty bug queue.

    While AI is reducing the _quantity_ of programmers needed in many cases, it is also an output multiplier for the remaining programmers, while often raising the bug-to-code ratio.

    AI has led to more output, more projects, and more bugs.

  7. pickleglitch

    I'm not a big fan of AI, but we are expected to use it at my job. In my position, it wouldn't really matter how good AI is, because when we find a bug it will often take an hour long meeting, or even multiple meetings, just to figure out what a given behavior should actually be before we can even attempt to fix it.

  8. drltaidev

    There's a chicken and egg story here as well: AI speeds up everything so the amount of code written is much higher, which does still contain bugs, even if AI can mostly solve them as well, new code will keep being written as well... That doesn't mean AI tools aren't good, but obviously they aren't perfect either. Luckily...

More from this day

2026-11-16