103 points by ex-aws-dude 4 days ago | 117 comments | View on ycombinator
frostiness 4 days ago |
td521534f12 4 days ago |
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.
fishtoaster 4 days ago |
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.
yokuze 4 days ago |
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.
GuB-42 3 days ago |
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.
undefined 4 days ago |
mattbrewsbytes 3 days ago |
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?
nzach 4 days ago |
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.
fritzo 4 days ago |
"Work expands so as to fill the time available for its completion"
davesmylie 4 days ago |
I can say our backlog of absolutely essential jobs that we haven't been able to get around to for the last 5 years is absolutely being smashed out one by one. A lot of this is unattended server migrations running over night being validated the next day.
The backlog as a whole though is growing as we have AI continually probing the infrastructure and various code bases looking for new security concerns or ways to improve performance and save money. Directly as a result of this, our cloud costs dropped massively in the last 6 months with only very minimal impact on performance.
I absolutely see a time in the not too distant future where all our infrastructure tech debt has been cleaned up, the security situation is as good as we can get it, the backlog has completely emptied and some of my team will be surplus to requirements.
g051051 4 days ago |
cmadar 3 days ago |
jjice 1 day ago |
For him, it really is helping him crush his backlog. It's a scale we forget about sometimes where you have hundreds of users, and not millions.
lordnacho 4 days ago |
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.
aynyc 4 days ago |
saulpw 4 days ago |
muzani 3 days ago |
AI is not a fine tool. It's one of the earlier stages of the crafting process. It's like a block of marble, roughly in the form of your sculpture, but you must continue to remove from it.
But if you're making rough bricks instead of fine art, then it's a perfectly decent tool.
pickleglitch 3 days ago |
cadamsdotcom 4 days ago |
That's not a place you want to get to.
jfrisby 2 days ago |
4 have zero backlog of any sort.
1 has a fleet of agents working through some product improvements that I postponed until the very end of the project. It's a very rote "rebuild this game on a modern engine" project to resurrect a game I developed 20 years ago, and there's a few small improvements I want to make to the game that deviate from the original. Today is day 5 of the rebuild, so it's not exactly a long-lived project per se -- but the bots did identify a bunch of defects in the original game and addressed them as part of the conversion project.
1 has:
- A few flaky tests to clean up. - A couple heisenbugs that I can't pin down until I get a couple PCs for testing (3D graphics stuff is Fun<tm>). - A whole lot of features that consist of one sentence I wrote down to avoid losing track of an idea, and which I may or may not ultimately choose to implement at all. - A couple issues that can't proceed until a human gets involved. I.E. I need to go through the hassle of setting up a corporation and setting up accounts with the various gate keepers (Apple, Google, Valve).
The biggest bottlenecks for me, at this moment are -- in descending order:
1. Running the linters / test suites / build processes for two of my projects completely slam my machine (load average hit 290 earlier today with 3 agents running things across the 2 game dev projects; CircleCI / Github Actions would be waaaay too expensive so I'm running it all locally until I can set up a CI runner node). 2. My bandwidth for acceptance testing, and other human-only work (read: game balance / play experience) 3. Weekly usage caps for fixed-price plans from the three services I use.
Setting aside my relatively unusual circumstances: At any business, you're going to have a problem of information rot when it comes to a backlog. The person who recorded a defect or feature request may not remember enough context to make it actionable (or they may not be at the org anymore). The assumptions underpinning the issue may or may not hold anymore (and it may not be clear which situation you're in). Etc.
Plus, there's going to be a not-unreasonable risk aversion to making changes that are in peripheral areas of the system that don't get a lot of attention -- lest fixing one issue cause some unexpected but undesirable outcome.
A lot of it mostly boils down to either "institutional knowledge gap" or "acceptance testing is a bottleneck".
adamtaylor_13 1 day ago |
What gives is most people work on decades old crusty crap, and they don't get to build from the ground up with AI.
You can't unstuck a system as fast as you can build it right the first time.
AnimalMuppet 3 days ago |
There is no guarantee that the new bug is not worse than the old bug.
For this reason, not every bug should be fixed. Especially, not every bug should be fixed and immediately pushed to production.
But maybe that wasn't the question. The question said "bug backlog". You could argue that bugs that we have chosen not to fix are not part of the backlog. Even so, fixing 20 bugs and pushing them to production may mean pushing 7 to 10 new bugs to production. Maybe you don't want to do them all right away.
hawkice 4 days ago |
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.
KronisLV 4 days ago |
Yup, I actually achieved that for a smaller system at work.
Tracked down and resolved every single logged bug there, alongside additional correctness improvements - after migrating the system from Oracle to PostgreSQL (it had a narrow enough domain where that was possible, made iterating way easier due to how easy it is to work with PostgreSQL and tune its setup for a specific workload), adding Testcontainers and pushing the test coverage to the high 90s percent, as well as migrating the front end from Vue 2 to Vue 3. Also wrote a custom load testing tool and improved the performance by up to 20x (though there were some really bad querying and N+1 issues at play).
It wasn't completely smooth and did create a few bugs along the way which also needed to be fixed, but overall was pretty solid - mostly due to the fact that the system had been developed with support for mock data from day 1 where you could spin up an instance and play around with pretty much anything you wanted. Hell, one could probably do a Rust rewrite of it if they didn't have anything better to do (not a Rust shop though).
That approach wouldn't really work for larger systems as is (e.g. there are some that are like around half a million SLoC), underdocumented systems, or systems where testing is contrived and difficult, as well as some stacks that just suck (e.g. bringing down a shared dev DB instance preventing N people from doing their work). Oh and also it took about an order of magnitude more tokens than would normally be given to your average dev.
Right now in my circumstances the bottleneck doesn't actually seem to be creating changes/features, but rather deployment and shipping as well as configuration management (assuming you have clients that need release instructions). Oh and being able to sell new work packages. Either way, in general you need more tests and specs than you think you do.
skyberrys 1 day ago |
undefined 3 days ago |
PeterStuer 4 days ago |
iotage 2 days ago |
This is exacerbated by giving a narrow prompt to fix a bug, will not magically result in a model being tasked to evaluate all the consequences and side-effects of changing code.
drltaidev 3 days ago |
efficax 4 days ago |
johnfn 4 days ago |
swader999 4 days ago |
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.
teo_zero 3 days ago |
So humans end up taking the final decisions and remain the bottleneck.
undefined 4 days ago |
0xbadcafebee 2 days ago |
d--b 3 days ago |
Doesn't mean we're getting unemployed, there is still a lot of things to do. Longer term projects, nice-to-haves we'd never have done before, experiments, experience improvements.
What is certain though is that we're not increasing headcount anytime soon.
getfacl 4 days ago |
seizethecheese 4 days ago |
There are many universes where the number of bugs grows faster with better agents.
theybash 3 days ago |
francisofascii 4 days ago |
sjrd 4 days ago |
[1] https://github.com/scala-js/scala-js/issues?q=is%3Aissue+sta...
johnshahbazian 4 days ago |
emscb 3 days ago |
koliber 3 days ago |
I no longer have a backlog. Every implementation idea that passes muster goes into development. Each sentry bug is investigated. I proactively do lots of “best practice” compliance things.
The client I consult noticed similar things. Development is now constrained around the pre development product tasks and post-deployment education and adoption of new features.
Aeseir 3 days ago |
Developing with AI is like 2 steps forwards and 1 step back in a blink of a eye.
The goal is to keep gaining a lot and losing a little.
rozenmd 3 days ago |
My feature backlog is now 10x bigger than it used to be, though.
Theophane_Rame 3 days ago |
wannabe44 3 days ago |
Kuyawa 4 days ago |
I haven't seen AI make a single mistake yet while coding my apps
guessmyname 4 days ago |
tete 3 days ago |
undefined 4 days ago |
bearjaws 4 days ago |
Thus Y is prioritized over bugs.
mock-possum 3 days ago |
SAI_Peregrinus 4 days ago |
Most of the rest of my solo projects are things where I want to learn something. Having an AI build the thing won't teach me what building the thing myself would. So AI is not particularly useful here either. Sometimes it can be good as a search tool or to provide hints, but it's mostly counterproductive.
The remaining two projects from my backlog where I just needed a tool specific to my own needs, I did with AI. They're OK, not perfect, definitely buggy, but they worked for what I wanted when I made them and none of the imperfections interfere with my use.
For my employer's projects, the backlogs are much bigger and the projects are bigger and still a lot of it can't be done solely by AI. And of course approvals become a bottleneck, but they also catch bugs. My job has legal compliance products, so we have an extensive QA & testing process which a "YOLO ship slop" approach won't work for.
rurban 3 days ago |
world2vec 3 days ago |
fnoef 3 days ago |
HoldOnAMinute 4 days ago |
david-green 3 days ago |
I'd also add that AI tends to find a way to churn out 1000-line changes when a judicious 3-line change would have served two years ago... i.e. teams risk drowning in PRs for features nobody cares about.
andrewstuart 4 days ago |
sailorganymede 4 days ago |
bob1029 3 days ago |
We could be in double digit issues completely blocked on the customer right now. I don't understand how some people think coveting a deep backlog of shit that isn't getting done is somehow a good thing.
brodydung about 8 hours ago |
samratkar about 6 hours ago |
jatin_builds about 22 hours ago |
colleentaylor10 about 20 hours ago |
darshilbabel 1 day ago |
nortiztech about 21 hours ago |
hzz4444433333 2 days ago |
inshopgroup 3 days ago |
haukebri 4 days ago |
esdg556 3 days ago |
betamatch 2 days ago |
abapforagents 3 days ago |
vaibhavtaprico 3 days ago |
singh_abinashi 3 days ago |
cby821555203 2 days ago |
jheriko 4 days ago |
ameynathe304 3 days ago |
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.