2 ms·
> You can’t fix everything Oh, you certainly can't. But you can choose how many things needing fixing you will make. Doing some shit without thinking and wait
by marcosdumay 3y ago
> You can’t fix everything
Oh, you certainly can't.
But you can choose how many things needing fixing you will make. Doing some shit without thinking and waiting for people to complain about symptoms of deep issues is a very effective way to create lots and lots of need for fixing things.
- mdaniel 3y agoAnd my experience has been that a quality culture like that can "resource starve" annoyances for literally years due to while True: ship_feature() if bugs: to_fix = highest_priority(bugs) fix = make_patch(to_fix) fix = introduce_new_bug(fix) # defer bugs[1:] until they meet the complaint criteria and that's how meetings end up with "but, how hard can that possibly be to fix?" statements
- NomDePlum 3y agoIf you accept some bugs as "features" that you will accept, not fix, you can have a bug free policy. Doing this means you make decisions early and don't carry a ton of historical baggage that gets endlessly discussed.
- hinkley 3y agoI knew a guy who said on a previous project they had a system that raised the priority of old bugs on some interval. I guess the idea was to either get them fixed or agree that they never would. There are morale and duplicate bug issues with keeping a backlog that grows faster than you can close them, so I guess that makes a bit of sense. And better than GitHub auto-shooting-the-messenger by clocking bugs after a month or two of inactivity.