3 ms·
I felt exactly the same. I read some of the original Second Sight reports and I very much got the impression that the issues were quite broad and related to ina
by ChrisKnott 3y ago
I felt exactly the same. I read some of the original Second Sight reports and I very much got the impression that the issues were quite broad and related to inadequate training, poor/confusing UI etc.
There isn't, as far as I can tell, a single interesting "bug" that was causing incorrect figures to be saved in a database, which is the impression you get from skimming the coverage.
- hermitcrab 3y agoMy father was interviewed for a potential job as trainer for the Horizons system many years ago. He was horrified by the attitude of the company running the training. Thankfully he didn't get the job.
- ndsipa_pomu 3y agohttps://www.theguardian.com/uk-news/2024/jan/09/how-the-post-offices-horizon-system-failed-a-technical-breakdown https://www.theguardian.com/uk-news/2024/jan/09/how-the-post... > One, named the “Dalmellington Bug”, after the village in Scotland where a post office operator first fell prey to it, would see the screen freeze as the user was attempting to confirm receipt of cash. Each time the user pressed “enter” on the frozen screen, it would silently update the record. In Dalmellington, that bug created a £24,000 discrepancy, which the Post Office tried to hold the post office operator responsible for. > Another bug, called the Callendar Square bug – again named after the first branch found to have been affected by it – created duplicate transactions due to an error in the database underpinning the system: despite being clear duplicates, the post office operator was again held responsible for the errors. There isn't a full list of the bugs produced, but it does look like a lot of bugs directly involved incorrect accounting to be recorded.