[bradjohnson]

I think the y axis: "% Bugs" in Fig. 1 has an incorrect scale. It doesn't add to 100%.

Also, it doesn't seem consistent with the claim: "Bugs discovered through Instabug are most likely to be resolved within 24 hours of being reported"

[barbegal]

Yeah going by that graph it appears that ~1.5% of bugs are fixed in 24 hours, ~5% within a week, ~10% within 30 days and only ~13% of bugs are fixed at all. That leaves 87% of bugs still to be resolved.

From the graph of total bugs vs time. It appears like at the current time ~10% of all bugs have been reported in the last 30 days. Even if all those bugs were magically fixed tomorrow, that would only be ~20% of bugs within 30 days so we can claim:

"Bugs discovered through Instabug are unlikely to be resolved within 30 days" and "1.5% of bugs discovered through Instabug are likely to be resolved within 24 hours of being reported"

[ericpauley]

The figure is showing percent of all bugs, not percent of resolved bugs. Likely the rest of the 100% is unresolved bugs.

The confusion on the second point hinges in "most likely". You're likely interpreting that as the expectation of resolution time whereas they are using maximum likelyhood estimation. MLE is rather useless in this case, but it is technically still correct.

[okgabr]

You’re right! Thanks for adding your thoughts to clarify. The wording “most likely” could be confusing indeed. How about we change it to be “Bugs discovered through Instabug are most often resolved within 24 hours of being reported.” Would that be clearer? And also saying that this is percent of all bugs, not percent of resolved bugs

[bradjohnson]

Yep, that clears up my confusion. Thanks

[darkhorn]

This is what happens when you hire computer science graduates as data scientists, you have incorrect data that you believe is correct. On the other hand those who hire statisticians are more successfull in collecting and analizing data.

[hinkley]

As one of my better bosses used to say:

    Graphs are for asking better questions, not for making decisions.

When I use graphs to brainstorm ways to verify the existence of a problem, I have a lot better time than when we jump to conclusions. There's something a little rotten in pretty much any projection of data that you try. Building policy off of a graph is a bad, bad plan.

Such a bad plan in fact that Mark Twain has a joke about it.