跳到正文
Hacker News (official RSS)(news.ycombinator.com)·· 6 天前品質評分42

Ask HN:AI 工具這麼厲害,為什麼待修的程式錯誤還是清不完?

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

重點導讀

有人好奇,AI 工具如果真能大幅加快寫程式,為什麼公司的待修錯誤和功能需求還是堆著?

  • 討論裡有人說,AI 助理雖然能修好眼前的問題,卻常只補上症狀,沒找出一整類錯誤的根源。
  • 團隊還得花時間審查程式碼,避免修好錯誤卻引發服務中斷。AI 助理也可能不熟悉整個專案,像剛加入的工程師一樣,只做區域性修改。這些經驗顯示,寫程式變快了,仍不代表工作能自動清完。
  • 判斷整體設計、檢查結果和確認產品好不好用,依然需要人。

AI 伴隨問答

自備 Key 深度分析

針對這篇報導有疑問?可直接點選快捷問題或向 AI 追問背景脈絡與技術細節:

正文

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

Image 1Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

[](https://news.ycombinator.com/vote?id=50520076&how=up&goto=item%3Fid%3D50520076)Ask HN: If AI tools are so good, why isn't your bug backlog empty? 14 points by ex-aws-dude56 minutes ago | hide | past | favorite | 11 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? help Image 2[](https://news.ycombinator.com/vote?id=50520822&how=up&goto=item%3Fid%3D50520076#50520822)nzach3 minutes ago | next[[–]](javascript:void(0)) 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. reply Image 3[](https://news.ycombinator.com/vote?id=50520828&how=up&goto=item%3Fid%3D50520076#50520828)td521534f122 minutes ago | prev | next[[–]](javascript:void(0)) 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. reply Image 4[](https://news.ycombinator.com/vote?id=50520260&how=up&goto=item%3Fid%3D50520076#50520260)frostiness43 minutes ago | prev | next[[–]](javascript:void(0)) 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. reply Image 5[](https://news.ycombinator.com/vote?id=50520624&how=up&goto=item%3Fid%3D50520076#50520624)ex-aws-dude17 minutes ago | parent | next[[–]](javascript:void(0)) 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 reply Image 6[](https://news.ycombinator.com/vote?id=50520806&how=up&goto=item%3Fid%3D50520076#50520806)philipwhiuk4 minutes ago | root | parent | next[[–]](javascript:void(0)) > 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. reply Image 7[](https://news.ycombinator.com/vote?id=50520765&how=up&goto=item%3Fid%3D50520076#50520765)cadamsdotcom7 minutes ago | prev | next[[–]](javascript:void(0)) 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. reply Image 8[](https://news.ycombinator.com/vote?id=50520781&how=up&goto=item%3Fid%3D50520076#50520781)jgalt2126 minutes ago | parent | next[[–]](javascript:void(0)) There's always post-mature optimization to work on. reply Image 9[](https://news.ycombinator.com/vote?id=50520788&how=up&goto=item%3Fid%3D50520076#50520788)johnshahbazian5 minutes ago | prev | next[[–]](javascript:void(0)) It's empty for all the projects I'm working on. Is your team just not putting in the time to fix them? reply Image 10[](https://news.ycombinator.com/vote?id=50520566&how=up&goto=item%3Fid%3D50520076#50520566)aynyc21 minutes ago | prev | next[[–]](javascript:void(0)) 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. reply Image 11[](https://news.ycombinator.com/vote?id=50520164&how=up&goto=item%3Fid%3D50520076#50520164)hawkice50 minutes ago | prev[[–]](javascript:void(0)) 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. reply Image 12[](https://news.ycombinator.com/vote?id=50520751&how=up&goto=item%3Fid%3D50520076#50520751)maxdo8 minutes ago | parent[[–]](javascript:void(0)) 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 reply
Image 13 Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | [Contact](mailto:hn@ycombinator.com) Search:

來源: Hacker News (official RSS) (news.ycombinator.com)
開啟原文

讀者討論

理性交流 · 即時討論