https://www.computerweekly.com/news/252498245/Post-Office-st...
According to one interview I heard, part of the problem is that the level of compensation that's actually required in this case is enough to render the Post Office insolvent.
Yes. And some families cannot be made whole; people killed themselves over this.
(Just as they did over false prosecutions from "erroneous transfers" due to technical card fraud, which a researcher once alleged in The Register was propagated by the IT staff of a British bank)
That would be good IMHO. Some people will disagree, but the post office going bust, and then nationalised would be a good outcome. It should never have been allowed to be privatised, it’s a national service, a place for providing contact to many different essential national provisions.
True it needed to cut costs, moving into smaller premises does that. Even the partnership with WH Smith’s and village news agents are sensible. But it should fundamentally be a government provision.
And while they are at it nationalise Royal Mail, and properly split Open Reach from BT and nationalise that too.
The Royal Mail was founded as a public service in 1516 by Charles I and was privatised in 2010.
The Post Office was founded as a public service by Charles II in 1660 and I believed privatised in 1969.
The Royal Mail are the people moving the post around, and the post office is where you go to post something if you're not going to put it in a post box, as well as do a lot of other things like renew your passport, change money into different currencies and you can even bank cash there.
The Post Office retail chain was split into a subsidiary of the Post Office corporation called Post Office Counters Ltd in 1987, which was renamed to Post Office Ltd in 2001.
When Royal Mail Group was privatised in 2013, the loss making Post Office Ltd retail business was retained by the government.
[1] AFAICT the prominent use of "Royal Mail" for the postage side of the business seems to be fairly recent, post-GPO era thing as well?
I strongly disagree. This mismanagement was going on long before the PO was privatised. In fact I'd argue that it was never really privatised.
We don't need a national postal carrier; a lot of post is now carried by private competitors. The Parcels operation is overpriced. Telecom has been hived off, long ago. What remains is a delivery service; and a network of Post Offices and pillar-boxes. I would instead (a) privatise the carrier service; and (b) nationalise the network of drop-off points, and make that available for use by any carrier. The PO shouldn't be things like a bank, a travel agent, or a delivery system for Social Security.
BT has similar problems, being the other graft from the same stock. I don't agree that OpenReach should be nationalised; OpenReach needs to be exposed to the bracing breeze of competition. It's currently effectively a monopoly.
the only shareholder is the secretary of state for business, energy and industry (which you can see in its accounts)
From a legal perspective that shouldn't be a problem, and isn't a good argument for lesser compensation. Either Post Office Ltd can get a loan, get bought or go bankrupt, like any private company. If it's the last one that will obviously create political fallout, but resolving that isn't the job of the justice system.
Not against the software developer? Let's wait and see whether they did due dilligence, shall we?
This happened over a very very long period of time.
People committed suicide over these false charges. Ruling out prosecuting the developer if it can be proved that they knew, did nothing, colluded in silence, etc., would be insane.
FWIW, I don't think "public prosecutors" in the conventional sense (Crown, CPS etc.) were even involved here. The Royal Mail is (like until recently the RSPCA) one of the few entities in the UK entitled to bring its own prosecutions. The Royal Mail pretty much invented the concept of formal investigation and prosecution. This is the Post Office acting with the assumed prosecutorial power of the state; the CPS may not ever have been involved.
No, the ability to bring a private prosecution is not restricted to specific entities - it is a right everyone has (though some offenses can only be prosecuted with the consent of the DPP, and the DPP can choose to take over a private prosecution) [1]. For example, a woman tried to crowdfund a private prosecution for rape [2].
From [1]:
> There are a number of organisations that regularly prosecute cases before the courts of England and Wales but they do so as private individuals, using the right of any individual to bring a private prosecution. One example is the RSPCA.
[1]: https://www.cps.gov.uk/legal-guidance/private-prosecutions
Though strictly speaking, before the concept of the "private prosecution" was formalised in law, the Royal Mail already had prosecutorial powers; it has always had prosecutorial powers. (The Royal Mail basically invented investigation-backed prosecution in the 17th century).
The Royal Mail is for sure one of the only major organisations to do it at scale too -- though the RSPCA did. The RSPCA have announced that they will no longer do it at all (not least because they have a terrible record of poorly founded and abusive prosecutions and had their arses handed to them in the High Court).
The point I was making here is that this investigation would never have gone to the police, because they have always reserved and widely wielded this power to investigate and prosecute. The Royal Mail even prosecute dog owners whose dogs bite postmen.
[0] which if you think about it presumably now imperils some individuals in a way that is distinct even from the extent to which Royal Mail (and Post Office Ltd) are vulnerable corporately.
This should also include developers doing code review of the code in topic, but also all related code, all testers/QAs and product owner. There isn't one developer that missed that bug.
What I do think is that anyone who pretended there wasn't a mistake, downplayed it when they knew it could be causing the prosecutions or even significant reconciliation issues, should be looked at.
First and foremost, in the UK, Fujitsu itself can (and I think should) be prosecuted for corporate manslaughter here if there is any evidence that Fujitsu executives conspired with the Post Office to keep this quiet, ever.
If anyone ever ordered a developer not to go public with their complaints, threatened a whistleblower, deleted evidence, that should crush Fujitsu for good.
But yes, individual executives should be at risk (the corporate veil can be pierced to include directors), and it's difficult to see how it is possible to rule out right now that there is real liability down the chain.
The situation at the Royal Mail is likely to be dramatically more serious, because there's a significant chance they were both covering up serious failings and knowingly directly prosecuting people to do so.
I worked in a highly regulated company, we were under supervision of FDA, EMA and German EMA. We once missed a bug in database migration where a boolean field was false by default in java (non-nullabe), but it could be null in database column. It apparently broke a few reports (NOT running software, just pdf reports) for pharmacological clinics, 2 developers, 2 testers, our PO and out CTO had "disciplinary" actions (don't remember what it was really called) and their actions were under supervision from external consultants our company had to pay for.
It's crazy we don't have such rules in finance, food, data processing and publishing industries.
> The situation at the Royal Mail is likely to be dramatically more serious, because there's a significant chance they were both covering up serious failings and knowingly directly prosecuting people to do so.
Yes, RM decided to start internal investigation that lasted a few years, instead immediately contacting police, this is why it lasted so long and were so many victims.
Yes, but the distinction here is not actually as useful here as you might think.
In this situation, Royal Mail _are_ the police (the USPS has its own police too). But Royal Mail are also the prosecutors in court (they have/had prosecutorial power).
They didn't really delay sending it to the police because they never would have. It wasn't a police matter because definitively it was a Royal Mail matter. (The Royal Mail has had the power to investigate and prosecute since before there even were police.)
Edit to add: it is now a "Post Office" matter as well because they are distinct businesses as of 2013, and Post Office Ltd is an ordinary company. But the key period concerns a time when they were one and the same
It is a longstanding power the Royal Mail had, in fact.
But yes, private prosecutions are protected by law and Royal Mail now prosecutes using the right of an individual RM employee to bring the charge.
So the bit I want to read up on later is exactly who the individuals were in each prosecution. Is it the chief executive?
Any kind of certification in this space have you have the following for developing core functionality regarding financial data:
* Proper definition of hard requirements and acceptance tests. * Developers have to develop and write tests against this specification. * Another developer have to perform a review and sign off that this code indeed lives up to this specification. * QA will run tests that verify the specification is met, and sign off that it met specification.
That is a PM/PO that have responsibility for the specification. At least two developers and a QA person that have verified that the specification was met. A bug like this only goes live due to impossible to meet deadline or incompetency on multiple levels.
The only remotely acceptable explanation would be that this is the result of some really weird edge case or possibly race condition. But in that case we're back to incompetency, since no experienced developers should design financial software without well known patterns and technologies for the core of the application.
In this particular domain there is zero excuse for a bug like this.
The way developers can be at fault here is if they managed to conspire with QA or testing to hide the existence of the bug from their management and continue to deny it when asked. Which implies a pretty toxic workplace, but, then again, Japanese conglomerates are not famous for sunshine and daisies.
And sure enough, that's the claim: https://www.computerweekly.com/news/252496560/Fujitsu-bosses...
The question is how those people who discovered the bug or managed the components in which it exists handled themselves.
There is no way that Fujitsu (or even individual Fujitsu employees and directors) should be considered off the hook just because software is only software, which is the defence I am seeing here and elsewhere. It should depend on how they acted.
What actually happened here is that some people dared to question the hierarchy. Since that was unpossible - underlings can never be allowed to question hierarchy - it turned into a political circus where the authorities spent insane amounts of time and money trying to maintain an established order that was in fact broken.
If this seems extreme, consider that in a functional system someone would have said "Wait, that looks wrong, we'd better fix that." There would have been some inconvenience and expense and possibly some awkward questions. But it was essentially a trivial issue, and the cost-to-fix would have been far lower than it will be now.
Dysfunctional hierarchies are defined by this kind of refusal to deal with reality when inconvenient facts are presented by those who are considered subordinate.
It literally becomes more important to punish those who challenge authority than to fix the real problem.
1) the justice system will not easily go against any government organization (because government has decreed that individual government workers carry responsibility "by default" for what the government does, unless the employee can prove the government maliciously caused the mistake (just causing the mistake, for example with bad info, is not enough), as opposed to the private sector, where businesses are "by default" responsible for mistakes, unless the business can prove an employee to be malicious) This means in a lot of cases judges have a choice when the government causes damage: destroy an employee's career AND giving them a very large fine, to be paid personally, or do nothing. Going after the individual is so unfair this is rarely done. That is probably exactly the intention.
2) government organizations, all of them, have legislative power to some extent (sometimes only over their own internal procedures. However, generally, it goes further. For example, the NHS can refuse care to an individual at their own judgement. Private MD's, by contrast, cannot refuse "basic" care, and can certainly not make that judgement themselves)
3) the justice system will only move against it's own people with extreme reluctance. Certainly mistakes won't be punished (they do this while repeating "how much responsibility they need to shoulder" at every turn. Asking how much responsibility it really is if there's no personal or even organizational consequences when they screw up is not appreciated. They have about the same level of responsibility as the player does in GTA5)
So, you don't do business with local governments as a consultant ("other" governmental organizations, from National Government over ATC to NAVO offices, are fine)
1) The justice system will not go easily against any large organisation unless they believe there is a case to answer. It isn't about whether something bad happened, it is whether somebody could be guilt in law. Governments blame their workers by default? Based on what? Going after the individual is so unfair? Again, that is simply not true. If an individual breaks the law, they will be prosecuted if there is a good chance of a conviction. The reason they don't always is because incompetence is not illegal.
2) The government organisations do NOT have legislative power. The NHS doesn't make up the laws, they abide by the laws of the land. They have some latitude within law but they are (and often are) still subjected to legal action both personally and corporately.
3) The reluctance is not against "it's own people", the judiciary is not the government in the UK. Again, there are laws which protect politicians from certain decisions but they are not above the law.
Of course, there is always the potential for hidden pressure to make problems go away etc. but most of what you say seems to be inferred from prejudice, not from facts.
1) For example, read https://www.civilservant.org.uk/ethics-no_minister.html (skip to the section on liability, if you must, but ideally don't)
For a more practical story, read, for example: https://www.noblesolicitors.co.uk/about/indepth-misfeasance....
That points out government workers, in particular police officers, can be held personally and even criminally liable for illegal actions, while at work. Illegal actions, of course, mostly constitute mistakes. But, this is law ... "not knowing the law is no excuse". Whereas not reading the employee handbook can get you fired, but it can never result in liability, never mind criminal persecution. If, in the private sector, your boss orders you to do something illegally, for example drive away with a car the company doesn't own, you are not liable, even if you knew that it was a crime.
In the private sector, it is up to the public prosecutor to prove you maliciously committed a crime while at work. For instance, if you stole a car, a prosecutor will have to prove that you personally benefitted and not just your employer to get a conviction.
By contrast, there is no such requirement for police misfeasance. If a police officer impounds your car for what turns out NOT to be a crime, he cannot avoid personal liability by, even correctly, claim he did not know X is legal.
The police force, or the ministry of Justice is NOT liable, by contrast, unless the public servant involved can prove he was given malicious instructions. In other words: in order to make the police force liable the individual officer has to prove he was given illegal orders at least.
See the turnaround? In the private sector companies are liable "by default". In the public sector "public servants", individuals, are liable "by default". The burden to prove it was someone else's fault shifts.
It's not just police officers, some very famous cases involve doctors being held personally liable for mistakes that are clearly the consequence of an understaffed emergency department. It was NOT the fault of the hospital, or the NHS, that wasn't even seriously discussed.
2) Google "Hierarchy of law". Law is not the exclusive domain of parliament (or rather: in many, many cases parliament has left implementation to government organisations that internally decide many aspects of law)
Specifically, Secondary (or "delegated") legislation in England includes:
Statutory instruments and ministerial orders By-laws of metropolitan boroughs, county councils, and town councils
https://www.lexisnexis.co.uk/legal/guidance/secondary-or-del...
City hall is one example that definitely has (limited, but even parliament is limited) power to create laws. What many people don't realise: so does the BBC, the NHS, ATC, airports and the phone company.
Generally, most government organisations have their own statutes that are special in the sense that they don't affect just their own organisation (like anything in the private sector), but everyone in society. They are law, and you can be convicted in a court of law for violating them. So yes, most government organisations write their own laws.
3) While technically true, how do you think it works in practice? The Judiciary is, more or less, "middle management" of the police force. Perhaps a bit higher than a line manager, but for example a public prosecutor gives orders to police officers, in any specific case (they decide which actions are taken when a theft is investigated, as opposed to where a traffic cop goes), and they get orders from judges in various capacities (e.g. investigatory judge). They work in the same offices, in the same building. Recently on a documentary there was a case of a police officer being 100% assigned to a particular prosecutor, not to do police work, but as a clerk of sorts for fraud cases.
There is not "the potential for pressure" here. The people that tell police officers what to do have a right of sorts called "prosecutorial discretion": they can, legally, forgive crimes of someone else (subject to some limits, but the only significant limits are geographical and that it doesn't include first degree murder).
When right above you in the management chain management there is someone that has the power to make specific instances of crime legal. What exactly do you think the "workers" will be demanding?
The problem is that, unlike forensic analyses and other scientific methods, the likelihood and nature of software errors is totally unpredictable.
Most regular people would expect an accounting software to maybe have UI bugs, or being occasionally unavailable, or any other number of annoying, but ultimately insignificant issues. They wouldn't expect it to mess up accounting.
Software is only "eating the world" because people trust its usefulness. At some point I wonder if we as an industry are not about to teach the world that software is not to be trusted, at least not for high-stakes situations. This is not the only example, think also about e.g. the Equifax security breach or the Boeing 737 Max disaster.
Poor taste to conflate a nothingburger with the deaths of 346 people.
I don't think judges would be implicated here. the court relies on expert witnesses to explain what to do with a piece of evidence.
For example, if someone is convicted based on DNA evidence, you would have an expert in DNA matching explain the probability of this happening by chance.
If a supposed expert in the software testified that this is impossible to happen unless money actually went missing, and that witness appeared credible, then what can you do?
Unless these cases were tried without juries, then the judge's responsibility is restricted to ensuring the case is conducted properly; that both prosecution and defence evidence is heard, and that only permitted evidence gets presented to the jury. It's not the judge's fault if some witness lies to the jury.
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.
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.
A software error needs to be calculated for. This is technical reality that cannot be changed as of today. Of course that also implicates other industries like banking.
I don't think the UK government has enough money to compensate the people it wrongfully convicted. It is harrowing mismanagement that the software wasn't tested immediately before any conviction. Everyone failed here aside from the postmasters themselves.