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

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?

21 points | by ex-aws-dude 1 hour ago

14 comments

  • td521534f12 11 minutes ago
    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.

    • bestouff 6 minutes ago
      I was going to say that. Solo projects advance fast now, and bugs are very few.
      • risyachka 4 minutes ago
        Feel free to share the product if there are really so few bugs
  • frostiness 52 minutes ago
    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.

    • ex-aws-dude 26 minutes ago
      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 a still a lot lost between sessions

      Its 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

      • philipwhiuk 12 minutes ago
        > It makes me wonder if it could be solved with better context management

        There's a reason that repos are now bloated with AGENTS.md files that try to cram context in as pre-text. And that there's so many vibe-coded context/memory aggregation frameworks.

        It's an AI-hard problem.

    • shipsafestack 10 minutes ago
      [flagged]
  • saulpw 1 minute ago
    The VisiData backlog is basically empty: https://github.com/saulpw/visidata/issues
  • fritzo 6 minutes ago
    Parkinson's Law:

    "Work expands so as to fill the time available for its completion"

    https://en.wikipedia.org/wiki/Parkinson%27s_Law

  • nzach 11 minutes ago
    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.

    • malfist 1 minute ago
      I'm not sure how you can claim it takes time to build trust with AI as if AI isn't actively demonstrating every day why it can't be trusted. Just this morning I had it review clinical notes from a procedure I had done and it mathed things wrong (declaring an injection was 2.5ml when it was 2ml of one thing plus 1ml of another).

      I ask it to fix one bug and it introduces three more. I ask it to add a feature and it adds four features.

      It has very little common sense. I asked it to build a feature that required api calls to openai, and it decided the best approach was to hand roll the interface code with some bonkers defaults (explicitly zero retries, explicit 1 second timeouts to non steaming api) and wrote the most fragile code that didn't generally work. Even when directed to use the published library by openai it still tried to apply its insane invited requirements to make even that fragile.

      I don't think it's nobody knows how to use it, its just not that reliable.

  • cadamsdotcom 15 minutes ago
    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.

    • jgalt212 14 minutes ago
      There's always post-mature optimization to work on.
  • sjrd 3 minutes ago
    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...

  • g051051 5 minutes ago
    Because just like without LLMs, focus is on delivering new products and features, not on paying down technical debt.
  • johnshahbazian 14 minutes ago
    It's empty for all the projects I'm working on. Is your team just not putting in the time to fix them?
  • aynyc 30 minutes ago
    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.
  • hawkice 59 minutes ago
    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.

    • maxdo 17 minutes ago
      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.

      You can calm yourself and say we can attack and move upstream, e.g. instead of using crm lets write our own crm, etc. But if everyone else is doing so, what is the end game lol

  • andrewstuart 1 minute ago
    Scope creep scales, that’s why.
  • sailorganymede 6 minutes ago
    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!