And that's what we need to be really, really mindful of and what we need to strive to look for so that we can get as much done in as little time as possible.

Another factor when it comes to bug priority is, is the fix safe, quick and easy?

So if a feature or a solution to a bug is safe, quick or easy, then there's a very good chance that we might as well just knock it out and move on.

However, we need to be super, super careful about this because oftentimes something can look safe and look easy only for us to find that it's an entire can of worms that once we open it, we're on a downward spiral and we can't find our way back out.

Like, you know, it just gets out of control really quickly.

So we have to be really careful about that.

Fellow programmers or game developers might have, you know, experienced this phenomenon before where it's like the easy bug to fix takes like a month to fix, but the hard bug to fix takes like one day.

This is a common thing that happens and our ability to, you know, accurately assess what's easy and what's not

with you know an incredibly high degree of certainty is just something that's really hard to do uh we can't do it to a certain degree but it's just kind of hard and it bites a lot of game developers in the butt the next thing is do we know how to fix it so if we don't know how to actually solve a particular bug right away it might be hard for us to prioritize it when if we have no real direction or leads on how we want to solve it so one example can be a common