Fix the bug that actually matters?

[TaleraRistain]

even Q&A cannot catch all bugs. thats unrealistic since Q&A is not testing on a live server.

from what appears to happen, its when the servers are under load according to the release, which since they did not say what kind of load, its likely the devs had to go over logs to try and determine how it happens and may not have been able to be replicated in their test environment. Since it has been cleared, clearly it was not happening 100% of the time, which are some of the hardest bugs to root out. the devs where I work see this with our software, and its called "unintended application". It cannot really be "tested" because its not a workflow the devs OR Q&A had thought of or would use. could they have caught it? sure, maybe, the number 0 one, most likely, this one I am not so sure because the test server, no matter how close you make it to live, will never be a live server.

The 0 bug from what I understood was an issue with systems communicating with each other and it's entirely possible they had test versions of those servers where it didn't manifest that bug, most likely because they weren't using the same API calls and endpoints the live servers were. As you said, no matter how close you make it to live, it will never be a live server.

Like you said, software QA is never going to catch everything. I would also be curious how the scale and scope of their systems have changed. My company has been having more bugs because we're migrating to new systems, adding more systems than we have now, and integrating AWS into our processes. When the scale increases, the likelihood of bugs does, too, and they can be more widespread or affect more things. I would think there had to have been some changes going on behind the scenes since they're working on a significant graphical upgrade.

The Caloric bug is one that prevents people from clearing. This is not a good thing. It would have been good if Square prioritized this one, but it appears that they didn't.

I wouldn't say it's necessarily they didn't prioritize it. It's probably more complicated. Something people on the outside may not realize is that the release of bug fixes isn't entirely based on how severe they are. They probably have a couple team members working on some other bugs while other devs puzzle this one out and those were faster to get ready to go than this more complex issue.