This is just another example of blaming the QA team for all the shortcomings of management and the developing team. <br><br>First, there's no reason why submitting a large amount of minor bugs would bog down the developing team. All developing teams set priorities for their bugs in their bug tracking systems. A method akin to triage where defects are labeled as Critical, High Priority, Low priority, and so forth. The actual labels vary from company to company, but it's pretty much the same. <br><br>More often than not, it's the developing teams poorly writing code and incurring what the industry calls code debt where fast solutions are chosen instead of robust ones because they are faster to implement, but they are more prone to failure in larger scopes. The reasons for it can be crunch, unrealistic deadlines, lack of management.<br><br>Even more important, top level management constantly hampers the developing teams and QA teams by setting impossible deadlines, giving QA a couple of days to test something that would take months, restricting access to all the resources/information needed for testing, setting pointless guidelines for defect report writing. This happens because management usually have no idea how QA works, or how long it takes, or don't care and see QA as the bottleneck to the quick releases they want.<br><br>At the end of the day, if developing companies did their jobs properly, QA would have no job, and no defects would appear.<br><br>Regardless of if the company doing QA treats their employees like dirt, which most software companies in general do anyway,  this leak feels a lot like someone trying to shift the blame from the developing team to the QA team.