Startups have to rediscover zero bug bounce
324,015 次观看
35 条评论
评论来自 X (Twitter) 上的原帖

@override_net
claude, remove all P2 bugs before adding 20 new files, don't make mistakes.
15 个赞

@finexma
Zero *known* bugs. I see what you did there.
14 个赞

@garrytan
Haha but you should know most of them if you are manning the customer support box well
12 个赞

@Afrye262632
Yes! Priority order = 1: Production Issue 2: User Experience Bugs (broken) 3: Feature Bugs (not working the way we hoped) 4: New features (Re-prioritize 3 & 4 by product impact and release schedule)
6 个赞

@ronburr
Great way to stave off, and work off technical debt, every 4th sprint (can vary by need) is dedicated to bugs and debt rearchitecture. It sounds expensive but it pays off and the team loves getting to the work they know needs to be done that is not a new feature
6 个赞

@MightyMogomra
Zero bug bounce is a sacred ritual wherein the Microsoft PM closes all the bugs that are open, and if nobody fights hard enough to reopen a bug it's considered finished forever
5 个赞

@esmeyury
Every sprint we get all bugs to zero. It's so painful to watch 30% of the sprint go towards fixing bugs every week... but it's probably worth it
5 个赞

@BrandGrowthOS
this applies to AI agents too erika's been in production for 8 months processing 200+ expenses monthly. we do weekly "zero error audits" - review every miscategorization, failed webhook, timeout the temptation is to ship new features when the agent works "mostly". but those edge cases compound fast at scale learned this the hard way when erika crashed processing 500 invoices at 2am. now we fix every known issue before adding capabilities craft matters even more with AI - one bad decision multiplies across thousands of transactions
3 个赞

@Chain_AlphaX
Code rekt? WAGMI with zero bugs
1 个赞

@joaquinrichards
@maraoz 👆🏻
1 个赞

@xdotli
Dang it i really love @supportingden and spent many afternoons trying to make it work (pivoting to a new co thus great chance to switch out of slack). But the day when i had to send out invites to friends den just broke - cannot access channels and cannot paste links etc. Had to bring everybody to (and locked with) slack.
1 个赞

@Vamzzz93
The CEO of YC reminding devs to fix their bugs, what’s happening. Are y’all consciously tolerating bugs?
1 个赞

@AdityaMullick7
The # of P2 bugs probably has gone up by 10x from LLM coding and those bugs become more difficult to identify and fix over time, so definitely agree. Bug fixing sprints should be more baked into these AI coding tools
1 个赞

@liquidsunlabs
insane slop posting
1 个赞

@isb
Or alternatively.. always prioritize some p2 bugs every release. Fixing these annoyances constantly delight customers - Github did this with Papercuts.
1 个赞

@nishan3000
Just yesterday, Claude Code told me exactly this when I wanted to continue building new features.
1 个赞

@RealPatternLab
a good reason to track/measure everything: sometimes the best way to remove the bug is to remove the feature, if its adding little value.
1 个赞

@rohan1357
I'd say that spending a tad bit more time in your V1, can sharply reduce the cost of p1, p2 bugs. And for every V1 you ship, there must be a follow-up V2, V3 otherwise you will only accrue more and more tech and UX debt.

@Swedish_chef
People love building low quality messes though

@abh1sek
I think it needs to be non-linear a bit, especially for startups. For every set of bug, have a framework’ish solution that eliminates the class. Especially true for security bugs which impacts trust.














