| ▲ | Ask HN: If AI tools are so good, why isn't your bug backlog empty? | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| 32 points by ex-aws-dude 2 hours ago | 49 comments | |||||||||||||||||||||||||||||||||||||||||||||||||||||
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? | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| ▲ | td521534f12 37 minutes ago | parent | next [-] | ||||||||||||||||||||||||||||||||||||||||||||||||||||
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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||
| ▲ | frostiness an hour ago | parent | prev | next [-] | ||||||||||||||||||||||||||||||||||||||||||||||||||||
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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||
| ▲ | fishtoaster 21 minutes ago | parent | prev | next [-] | ||||||||||||||||||||||||||||||||||||||||||||||||||||
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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| ▲ | lordnacho 11 minutes ago | parent | prev | next [-] | ||||||||||||||||||||||||||||||||||||||||||||||||||||
Last year during the summer I had a bunch of things I wanted to do to improve on the trading system I was working on. A bunch of things that were mostly fiddly, which I had estimated would take me 6 months. Someone told me to try out Claude Code during my holiday. I learned the backstory of Sauron with a friend while getting the entire backlog cleaned up. Things worked, better and faster and more maintainable. Did I run out of things to do? Well, the firm I was with didn't know what they wanted built, so it was a lot of not getting anything done while waiting for them. But the things they had previously wanted, yes, they were done. | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| ▲ | PeterStuer 8 minutes ago | parent | prev | next [-] | ||||||||||||||||||||||||||||||||||||||||||||||||||||
On the project I am working on atm, I think I am averaging a net addition of around 50-200 production LoC per day. The system produces around 10x as much test-harness code (feature + regression). Planning/exploring takes about 1/4th of the time, coding 1/20th, documentation 1/10th and testing all the rest. Backlog has no known bugs, quite a few de-prioritized very niche edge cases that in theory could arise but never showed up in production, but still could be nice to haves, and plenty of new desired functionality. I'm sure I could go 10x faster, but I choose not to as this pace nicely balances cost, progress and keeping it under control for me. | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| ▲ | johnfn 9 minutes ago | parent | prev | next [-] | ||||||||||||||||||||||||||||||||||||||||||||||||||||
Because some bugs are underspecified, and the specification is the remaining work. For instance, "I can add the same meal to the meal catalog twice". That's a bug. But how do you solve it? Do you merge them? Do you error on the second attempt? Maybe you allow for two variations of the same meal? Once you specify the bug then you can toss it into an LLM and it's done. If you toss it into an LLM without doing that it might solve it in a way you don't like. | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| ▲ | nzach 38 minutes ago | parent | prev | next [-] | ||||||||||||||||||||||||||||||||||||||||||||||||||||
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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||
| ▲ | efficax 11 minutes ago | parent | prev | next [-] | ||||||||||||||||||||||||||||||||||||||||||||||||||||
I feel like you could only ask this question if you don't really understand software development. If you're building features, you're building bugs. Nobody ever said AI produced bug free code. But it does make it possible to evaluate code extensively to find bugs before you ship it. I believe the code I'm shipping now has far fewer bugs than ever before, but bug free? I don't even know if that makes sense. it all depends on what ends up counting as a bug, in the end. | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| ▲ | saulpw 27 minutes ago | parent | prev | next [-] | ||||||||||||||||||||||||||||||||||||||||||||||||||||
The VisiData backlog is basically empty: https://github.com/saulpw/visidata/issues | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| ▲ | fritzo 33 minutes ago | parent | prev | next [-] | ||||||||||||||||||||||||||||||||||||||||||||||||||||
Parkinson's Law: "Work expands so as to fill the time available for its completion" | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| ▲ | swader999 15 minutes ago | parent | prev | next [-] | ||||||||||||||||||||||||||||||||||||||||||||||||||||
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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| ▲ | seizethecheese 14 minutes ago | parent | prev | next [-] | ||||||||||||||||||||||||||||||||||||||||||||||||||||
A hidden assumption in your question is that the ai tools themselves don't create bugs or new backlog items. This is false. Even with perfect AI tools, bugs would slip in because of imprecise specifications. There are many universes where the number of bugs grows faster with better agents. | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| ▲ | g051051 32 minutes ago | parent | prev | next [-] | ||||||||||||||||||||||||||||||||||||||||||||||||||||
Because just like without LLMs, focus is on delivering new products and features, not on paying down technical debt. | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| ▲ | sjrd 29 minutes ago | parent | prev | next [-] | ||||||||||||||||||||||||||||||||||||||||||||||||||||
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... | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| ▲ | yokuze 24 minutes ago | parent | prev | next [-] | ||||||||||||||||||||||||||||||||||||||||||||||||||||
> 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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||
| ▲ | cadamsdotcom 42 minutes ago | parent | prev | next [-] | ||||||||||||||||||||||||||||||||||||||||||||||||||||
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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||
| ▲ | francisofascii 12 minutes ago | parent | prev | next [-] | ||||||||||||||||||||||||||||||||||||||||||||||||||||
Our users don't have enough feature requests at this point. I have to be diligent in generating new ideas, features, improvements, etc. for the projects I work on. Otherwise we would run out of work. | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| ▲ | aynyc an hour ago | parent | prev | next [-] | ||||||||||||||||||||||||||||||||||||||||||||||||||||
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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| ▲ | Kuyawa 14 minutes ago | parent | prev | next [-] | ||||||||||||||||||||||||||||||||||||||||||||||||||||
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 | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| ▲ | hawkice an hour ago | parent | prev | next [-] | ||||||||||||||||||||||||||||||||||||||||||||||||||||
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. | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||
| ▲ | guessmyname 21 minutes ago | parent | prev | next [-] | ||||||||||||||||||||||||||||||||||||||||||||||||||||
My bug backlog is empty. My task backlog is not. | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| ▲ | johnshahbazian 40 minutes ago | parent | prev | next [-] | ||||||||||||||||||||||||||||||||||||||||||||||||||||
It's empty for all the projects I'm working on. Is your team just not putting in the time to fix them? | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| ▲ | bearjaws 26 minutes ago | parent | prev | next [-] | ||||||||||||||||||||||||||||||||||||||||||||||||||||
"Competitor X is working on Y, we need to beat them to it!" Thus Y is prioritized over bugs. | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| ▲ | HoldOnAMinute 25 minutes ago | parent | prev | next [-] | ||||||||||||||||||||||||||||||||||||||||||||||||||||
Even AI breaks things when trying to fix bugs. | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| ▲ | sailorganymede 32 minutes ago | parent | prev | next [-] | ||||||||||||||||||||||||||||||||||||||||||||||||||||
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! | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||||||||||||||||||||
| ▲ | andrewstuart 28 minutes ago | parent | prev [-] | ||||||||||||||||||||||||||||||||||||||||||||||||||||
Scope creep scales, that’s why. | |||||||||||||||||||||||||||||||||||||||||||||||||||||