Sometimes what's worse is when I am pretty sure something they suggest won't fix the bug and then it does fix it. Like I experienced a race condition in my Android email app and talked to support about it. They said try clear app data / cache and see if it worked. I thought there is no way that would solve it and they're just giving be the boilerplate support thing. It did fix it.

Now I'm even more scared at what their code is doing.

the dunning-bugger effect

"ugh I know exactly why this is happening" is such a frustrating feeling. Especially when it's stuff that should've been found in testing, or that you know probably was found in testing, but they deprioritized the fix.

Bugs frustrate me more because I can often guess at why they are happening and how to fix them but can't just apply the fix myself.

That's like a big portion of bugs lmao, lots of bugs exist because the spaghettification of the code makes it too costly to fix. Do you really think devs don't know why the bugs are there? They usually can't be fixed because there is no time or no willingness from management or the root cause is so deeply rooted it requires a shit ton of work to be able to fix it at all.

The DMR in call of duty years ago. "Here's a bug with a gun that instakills from 4 miles away that breaks the game dynamics. It's literally unplayable. Instead we added more features that make us money."