jm + support   5

Stop explaining black box machine learning models for high stakes decisions and use interpretable models instead
Via The Morning Paper:
Black box machine learning models are currently being used for high stakes decision-making throughout society, causing problems throughout healthcare, criminal justice, and in other domains. People have hoped that creating methods for explaining these black box models will alleviate some of these problems, but trying to _explain_ black box models, rather than creating models that are _interpretable_ in the first place, is likely to perpetuate bad practices and can potentially cause catastrophic harm to society. There is a way forward -- it is to design models that are inherently interpretable. This manuscript clarifies the chasm between explaining black boxes and using inherently interpretable models, outlines several key reasons why explainable black boxes should be avoided in high-stakes decisions, identifies challenges to interpretable machine learning, and provides several example applications where interpretable models could potentially replace black box models in criminal justice, healthcare, and computer vision.

I wholeheartedly support this idea, it makes a lot of sense to me in terms of producing ML/AI that can be supported operationally.
machine-learning  ai  ops  support  transparency  papers  black-box  models  computer-says-no  automation  explainability 
6 weeks ago by jm
Ask AIB -
AIB now have a dedicated customer-support forum on That is a *great* idea
aib  banking  support  forums  banks 
march 2014 by jm
an ex-RBSG engineer on the NatWest/RBS/UlsterBank IT fiasco
'Turning over your systems support staff in a wave of redundancies is not the best way to manage the transfer of knowledge. Not everyone who worked the batch at [Royal Bank of Scotland Group] even knew what it is they knew; how, then, could they explain it to people who didn’t know there was knowledge to acquire? Outsourcing the work from Edinburgh to Aberdeen and sacking the staff would have exposed them to the same risks. [...]

I Y2K tested one of the batch feeder systems at RBS from 1997 - 1998, and managed acceptance testing in payments processing systems from 1999 - 2001. I was one of the people who watched over the first batch of the millennium instead of going to a party. I was part of the project that moved the National Westminster batch onto the RBS software without a single failure. I haven’t worked for the bank for five years, and I am surprised at how personally affronted I am that they let that batch fail. But I shouldn’t be. Protectiveness of the batch was the defining characteristic of our community. We were proud of how well that complex structure of disparate components hummed along.
It was a thing of beauty, of art and craft, and they dropped it all over the floor.'
systems  ops  support  maintainance  legacy  ca-7  banking  rbs  natwest  ulster-bank  fail  outsourcing 
june 2012 by jm
ClamAV and The Case of The Missing Mail - Return Path Blog
version 0.94.x got end-of-lifed a year after the release of .95, to fix a bug that would increase bandwidth consumption on their mirrors. To mandate upgrades, the devs sent a kill-switch trigger to .94 installations in the field. chaos ensues, unsurprisingly
clamav  filtering  mail  ouch  upgrades  end-of-life  support  open-source  sourcefire  return-path  from delicious
april 2010 by jm

Copy this bookmark: