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

Do you have the experience of triaging bugs/features at work? There's always more problems then we can solve at once. There is only so many man hours/money/attention available.


I'm not sure which approach this analogy supports.

Sometimes it makes sense to fix small obvious issues quickly ("oops, forgot to check for null here") before diving into potentially worse but more complicated problems ("user who signed up on legacy plan reports that some playlists are incomplete in new app").

Sometimes there's such a high impact issue that you have to try to address it immediately, even if you suspect that it will involve a hellish trek through the least-maintained code in the whole company before you can even isolate a reproducible test case.

And if you have multiple developers working on bugs, one person may be doing the first while a different person is handling the second.


There are different ways/philosophies to triage; but the fact remains that you have to triage. That's all I wanted to argue. You have to pick and choose what to work on, so, in the context of environmental-protections, it's worth arguing the merits of different problems/solutions IMO.


ha. i was originally thinking performance optimizations but I like your example more




Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: