Discussion about this post

User's avatar
Alex's avatar

Just read some of the 2019 judgment

One thing that is extraordinary to me, is that the post office were claiming simultaneously:

a) That their software was fully robust

b) That (initially),when asked for records of the detection, analysis and resolution of bugs, that ‘no such document’ existed [paras 579 & 580 ]

These two claims are completely inconsistent with each other.

Any competent software company (and indeed, even most incompetent ones) has a ‘bug database’, ‘issue list’, ‘problem tracker’ or similar. To make software robust,you need to do two things:

1) The design needs to be such that all classes for which this is possible, cannot occur

2) Remaining errors are found, root caused, and removed

It is very unusual for 1) to be sufficient - it requires the complexity to be very limited. Horizon clearly failed on this count too, as its audit trail did not contain enough information to reconstruct what happened in the case of errors (which resulted in them accusing the SPMs of criminality). But you need a bug database to execute 2).

In summary, for the benefit of future litigation: If you’re going to claim, as a main part of your case, that your software is robust, then also saying you have no bug database is sufficient to refute this.

(The suggestion at 589 from counsel that it was merely a document on when you need to kick the printer is also laughable)

Expand full comment
Denis Howe's avatar

Thanks for clarifying this important point. As a computer programmer, I think everyone should be terrified that their life could be ruined by bad software, and it's horrifying that the law has been changed to make that more likely.

Expand full comment
17 more comments...

No posts