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?
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.
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.
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
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.
"Work expands so as to fill the time available for its completion"
https://en.wikipedia.org/wiki/Parkinson%27s_Law
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.
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.
That's not a place you want to get to.
[1] https://github.com/scala-js/scala-js/issues?q=is%3Aissue+sta...
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.
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