Ask HN: If AI tools are so good, why isn't your bug backlog empty?

ex-aws-dude 42 points 70 comments November 16, 2026
View on Hacker News

A lot of people outside tech ask me if AI is going to replace programmers and I just think: if that were the case we should be running out of things to do The bug backlog should be empty and we've caught up to every feature request from PMs to the point that we are bottlenecked on the business side But that does not seem to be the case with my own company or most devs I talk to in the industry So what gives?

Discussion Highlights (20 comments)

hawkice

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.

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.

aynyc

Mine is. I've been telling my senior managements that it's cheaper to rewrite stuff from scratch with AI then fix OLD products. They ate that up and everything we have now never reach v1.0 status.

cadamsdotcom

If you or your company has nothing to build it means they're out of ideas. And if they're out of ideas, they have too many people. That's not a place you want to get to.

johnshahbazian

It's empty for all the projects I'm working on. Is your team just not putting in the time to fix them?

nzach

AI only can improve velocity if it mostly works unsupervised. But most people don't trust their agents to run alone. And to build that trust will take some time, people will need to learn how to use AI effectively. I think the PS3 hardware could be a good analogy. It was really powerful, but nobody really knew how to use it. After a few years people got really good at it . And you can view this evolution by the improvement of graphical fidelity we got over the years.

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.

fritzo

Parkinson's Law: "Work expands so as to fill the time available for its completion" https://en.wikipedia.org/wiki/Parkinson%27s_Law

sailorganymede

Standards are super low, so slop gets approved and no one is checking. We get graded on how many Jiras we close. A bug gets a Jira. So we are doing great!

g051051

Because just like without LLMs, focus is on delivering new products and features, not on paying down technical debt.

sjrd

My bug backlog has been empty [1] at each release for 5 years in a row. We did not need AI to get there. [1] https://github.com/scala-js/scala-js/issues?q=is%3Aissue+sta...

andrewstuart

Scope creep scales, that’s why.

saulpw

The VisiData backlog is basically empty: https://github.com/saulpw/visidata/issues

bearjaws

"Competitor X is working on Y, we need to beat them to it!" Thus Y is prioritized over bugs.

HoldOnAMinute

Even AI breaks things when trying to fix bugs.

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.

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.

guessmyname

My bug backlog is empty. My task backlog is not.

swader999

Performance, Defect rate, feature velocity (5x), cycle time on defects to prod are all at the best they've been on our 7 year LOB 1.5 million loc system. 3 devs/2 qa, 2 sme's. 200 paying customers, moves money so it has to work. First time in 3 decades I don't have any tech debt that I NEED to tackle. Customers can't keep up with us. We are considering new products/adjacent markets. Strangely, our competitors (about 5 serious ones) don't seem to be matching us.

Kuyawa

Bug tracker is empty but todo list is full with things to work on and new features to add I haven't seen AI make a single mistake yet while coding my apps

Semantic search powered by Rivestack pgvector
13,334 stories · 126,150 chunks indexed