Those aren't bugs. The first was a fraud that developers actively participated in.
And yes, developers are pretty regularly "cogs in the machine" when it comes to define the development conditions. Especially in large corporations like Fujitsu.
They may not even be aware that they worked on this. Or they may have relayed concerns about schedule pressure making errors inevitable, or may be working in an environment where no such concerns can ever be raised.
It seems likely that they're working in the before-testing times which correlates strongly with risk of the above.
I wonder about the procurement process that lead to Fujitsu supplying the UK post office. This might be an instance of the public sector picking the cheapest from N bids then looking surprised when cheapest turns out to mean crap.
Yet how many times do we hear a senior manager or politician claim they "take full responsibility" but not resign, and then attempt to carry on as before?
"Taking responsibility" has become a meaningless phrase.
The reason for this is quite simply because it's impossible to develop bug free code. The process needs to reflect this, and if it doesn't it's not the individual developers fault.
This is often repeated by developers and it reeks of hypocrisy. Of course management must be implicated, but so must be the developers. Innocent developers are not simply helpless cogs in the machine coerced by management.
This blameless attitude held by many developers permeates the software industry. Whether it's the Volkswagen emissions scandal, ad-tech, or widespread online tracking - these were conceived, built and implemented by developers. And yet developers think they stand apart blameless from the consequences of their shoddy practices.
I wonder if the Fujitsi developers, far removed from the Post Office staff, have ever stopped to consider that the software they wrote ruined the lives of so many people.