I too believe LRU's a good way of working through issues, but with my current "side" (who am I kidding) project, there's issues and feature requests stretching back to 3 years ago that were legitimate but the previous maintainers just didn't have the bandwidth to address. Because of this, I have to resort to a two-pronged approach where I work the backlog down by resolving them in LRU order, and simultaneously ensure that new issues being added to the end of the queue are also addressed as quickly as possible to strike a healthy balance between fixing "legacy" problems and addressing new feedback. We also switched to a new develop/release model where issues need to be tagged with the backport label to indicate that the fix for it is critical and we need to make an out of schedule patch release to address it so triaging becomes especially important. And it's just something productive to do to pass away the time :D
Re: context switching, I'm a bit torn about how I feel. On one hand, going back and forth between things seems to make me bad at both. On the other hand, I agree with your observation that switching provides you an oppurtunity to reset and break out of your current mindset so you can return to the problem with a fresh approach that hopefully let's you resolve it quickly.
an oppurtunity to reset and break out of your current mindset so you can return to the problem with a fresh approach that hopefully let's you resolve it quickly.
It does help.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I rarely triage to be honest. Unless there is a dependency from one issue to another. I scroll to the bottom and work my way up.
I find context switching more refreshing because you get to let go of the current way of thinking.
I too believe LRU's a good way of working through issues, but with my current "side" (who am I kidding) project, there's issues and feature requests stretching back to 3 years ago that were legitimate but the previous maintainers just didn't have the bandwidth to address. Because of this, I have to resort to a two-pronged approach where I work the backlog down by resolving them in LRU order, and simultaneously ensure that new issues being added to the end of the queue are also addressed as quickly as possible to strike a healthy balance between fixing "legacy" problems and addressing new feedback. We also switched to a new develop/release model where issues need to be tagged with the
backportlabel to indicate that the fix for it is critical and we need to make an out of schedule patch release to address it so triaging becomes especially important. And it's just something productive to do to pass away the time :DRe: context switching, I'm a bit torn about how I feel. On one hand, going back and forth between things seems to make me bad at both. On the other hand, I agree with your observation that switching provides you an oppurtunity to reset and break out of your current mindset so you can return to the problem with a fresh approach that hopefully let's you resolve it quickly.
It does help.