Three in four (74.5 per cent) of these reported incidents took place in the United States.
Clearly nowhere else in the world has crime just because it's not reported as much.
And blaming poor code on apathetic developers is bullocks. Imagine the following meeting with higher management.
Manager 1. I delivered 2 projects on time and on budget.
Manager 2. I delivered 5 projects, all of which were completed early and under budget!
Higher management shower congratulations, praise and bonuses on which manager?
Was it the guy who diligently ensured that the job was done properly to the point of pedantry and delivered secure, stable, well tested and documented code while ensuring his team was kept well trained?
Or was it the guy who forced his staff to cut every corner, denied requests for training, eliminated testing and declared the program done and the project ready to deploy company wide shortly after a mostly working build was produced that should have been considered an alpha test. At which point having deployed the tangled mess it was declared to be the responsibility of the Business as Usual support staff since it was live code and not in development, to the deep joy of the support staff when they discovered the mess was not only a poorly coded disaster waiting to happen but had no documentation.
By which point like a hurricane leaving a trail of destruction he's doing the same thing to the next project and his staff can't be disturbed. Naturally. A cycle which continues until either something blows up that he can't pin on the Business as Usual staff and he's fired, or he's promoted. (either because management think he's doing a good job, or because everybody technical deploys the "failing upwards" technique of ridding themselves of somebody useless.
Once at such rarefied heights (where hopefully he'll suffocate) he has two options to explain the poor performance of the programs he's been responsible for. He can admit that all of his coding, working, supervisory and management practices are destructive and try to do something about the mess he's caused, or blame his useless and apathetic developers.
. . . so who do you think got promoted, and who do you think is at blame for the situation?